Chrome 135 (in Beta as I write, probably stable early April?) will have customizable select elements in it. You opt-in to it in CSS, and once you have, you can go ham on styling regular ol’ <select>, <option>, ‘n’ friends elements. Very progressive-enhancement friendly as a select without custom styling is… fine. It’s interesting and […]
The ability to style a <select> menu has long been high on list of web designer’s want lists. The inside part anyway; the part that opens up when you activate it. The outside we’ve been able to style for a while. Open UI did a bunch of research and even had a browser implementation of […]
We just looked at how “animate to auto” (e.g. transition from a fixed value to a keyword like auto, max-content, etc.) is “opt-in” in a sense. You have to use interpolate-size: allow-keywords; to make it work or use a function like calc-size(), neither of which you accidentally do. This is because research showed that it […]
A good point by Mayank: TheĀ multipleĀ attribute onĀ <select>Ā should pretty much never be used. It’s like the polar opposite of singleĀ <select>, where instead of universal familiarity, it has universal unfamiliarity. Perhaps its only saving grace is that I have yet to encounter this attribute in any codebase. HTML: The Bad Parts
Frontend Masters Donates to open source projects. $363,806 contributed to date.
