6 ms·
If this will stop the proliferation of terrible JavaScript implementations of <select>, I'm here for it.
by endemic 2y ago
If this will stop the proliferation of terrible JavaScript implementations of <select>, I'm here for it.
- drivingmenuts 2y agoI salute your optimism. Really, this just gives developers more options to make designers lives more miserable, and vice-versa.
- layer8 2y agoMy thought was it is giving designers more options to make users’ lives more miserable.
- jimbob45 2y agoThere’s got to be a happy medium between using canvas to make the controls you actually want and browser-provided one-size-fits-nobody controls. I really thought MS was onto something with Silverlight’s with XAML but that died.
- jjcm 2y agoI know LoC is a terrible metric, but it always shocks me that things like react-select require 30k LoC. 21% the size of the code of the Apollo Lander to configure/style a select dropdown.
- streptomycin 2y agoreact-select does a lot more than style the select though, so even after this new standard for customizable selects is supported everywhere, react-select will still have about the same level of complexity as it does now.
- riwsky 2y agoBut does it get even 21% of the way to landing on the moon?
- HelloImSteven 2y agoMaybe 21% of astronauts have used select components made with react-select. That’s approaching moon territory!
- ocdtrekkie 2y agoI am honestly just blown away Google invested effort into a web standard that actually improves the web versus the dozens of web platform projects designed to let websites slurp more data. This is something I actually look forward to being able to use when Firefox gets it.