Discussion
I suspect I will always think it was a mistake to allow author styling of `<select>` elements and sub-elements, and yes, most other form inputs as well.
I acknowledge the reasons for supporting it are valid and real, and also that I’m likely just being an old sourpuss. I nevertheless continue to believe user interaction elements should be consistent with the host operating system, so that users subconsciously know what a thing is when they see or otherwise interact with it.
Ah well.
@Meyerweb I may have similar opinions about cursors, and yet: https://github.com/w3c/csswg-drafts/issues/14251
Giving the increasing tendency of desktop applications using their own UI widgets, I'd dare say they are using the new OS standard.
Clients are always asking to style every UI element according with their own designs. The alternative to giving us the ability to style them is us continue making our own implementations. No joke.
Allowing us to style form inputs means better accessibility, and maybe even the ability to disable CSS and have a functional page.
@jcurioso As I said, I acknowledge that the reasons for wanting this, which you have now written out, are valid and real. This does not undo my feelings on the matter.
I will go even further: every browser should have a button in the main toolbar to disable CSS (displaying custom defaults), and every website should be doing an effort to be fully functional when that button is pressed, unless it is a Photoshop clone, for example. With a little push from the standards side, it should be achievable for 90% of sites. Plus, we would much better accessibility.
Reading mode is cool, but it is a poor surrogate, and it doesn't have the same goals.
@Meyerweb I think the logic is that after decades of people rolling their own, the native controls look just as foreign as any other. Allowing for more customization of the native controls improves the user experience in almost every other regard.