Modern browser features and javascript minimization #1520
domlen2003
started this conversation in
Feature Requests / Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Compatibility Clarification
Building on #1283 my first question is if there is a targeted browser version for bits-ui and shadcn?
I didn't find a compatibility spec anywhere, but if Baseline would be targeted, like e.g. Tailwind already does (so it would make sense for shadcn), new browser features can be assumend within the next few months/years that can simplify many internals of this library.
An easy change would e.g. be the scroll container which currently uses 'a lot' of css to hide the default scrollbar.
This is newly a baseline feature with
scrollbar-width: none;
https://developer.mozilla.org/en-US/docs/Web/CSS/scrollbar-width
Possible upcoming features
Simplifying current components
Popover API: https://developer.chrome.com/blog/introducing-popover-api
Commands: https://developer.chrome.com/blog/command-and-commandfor
Natively customizable selects: https://developer.chrome.com/blog/rfc-customizable-select
New components
Carousels will probably be possible to do completely natively:
https://developer.chrome.com/blog/carousels-with-css
Difficulties
I know most of these new features will not be drop in replaceable because of the
{#snippet child({ props })}
pattern which doesn't work for e.g.<summary>
because you need it to be that specific element.So some of this would require the process of making a new major version once a feature becomes baseline available.
Beta Was this translation helpful? Give feedback.
All reactions