Comment by drivingmenuts
2 days ago
It's a middle finger to people who try to set some standards and maintain them for a while. Also, a middle finger to accessibility people.
2 days ago
It's a middle finger to people who try to set some standards and maintain them for a while. Also, a middle finger to accessibility people.
It's absolutely not that- it's an early implementation of a drafted WHATWG standard in the "iteration" phase, put behind a development build and a development flag so people know that it isn't stable and might change and nobody who doesn't explicitly opt in will be affected. This is literally made to allow "people who try to set some standards" to test their proposed standards and iterate on them before finalizing the proposal.
As far as accessibility, the native browser select is almost always going to be more accessible than someone making a custom input using JavaScript so they can add some styling control. Having the native version support basic styling is a big accessibility win IMO, because it disincentives developers from making a less accessible alternative for the sake of matching some design file.
The middle finger is for people like you who didnt read the first paragraph.
> A customizable version of the select element is officially in Stage 2 in the WHATWG, with strong cross-browser interest and a prototype for you to test out from Chrome Canary 130.