fix: remove demo styling that causes rendering issues in the docs

[davidemarcoli]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves issues where the select docs didn't render in v5

📝 Checklist

• I have linked an issue or discussion.
• It's submitted to the main branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• I have updated the documentation accordingly.
• All tests are passing
• New/updated tests are included
• I have updated the "upcoming" section inside docs/changelog.md explaining the changes I contributed

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[colinscz]

It looks now much better, but I can observe a weird behaviour in local. Once I clicked through a couple of component pages I can click on other pages but the navigation doesn't seem to work anymore. The path in the address bar is updated but the navigation jump is not done.

@davidemarcoli can you reproduce this on your side?

[colinscz]

There seems to be still an issue with the virtual scrolling example at least in Firefox (but was already there before):

[davidemarcoli]

It looks now much better, but I can observe a weird behaviour in local. Once I clicked through a couple of component pages I can click on other pages but the navigation doesn't seem to work anymore. The path in the address bar is updated but the navigation jump is not done.

@davidemarcoli can you reproduce this on your side?

Yes, I can reproduce it. six-root seems to be the problem

[davidemarcoli]

There seems to be still an issue with the virtual scrolling example at least in Firefox (but was already there before):

Also happens on Edge. It's probably because we set the options after the component is created so the validation method already ran once before we set the options.