The element can now be customized with CSS *in Chromium browsers*
So at least 5 more years until in can actually be used.
The element can now be customized with CSS
41–50 of 194 posts
Re: The <select> element can now be customized with CSS
#42The fact that I'm disproportionally excited about this probably dates me as an early 2000s web developer. But since selects can do things that you simply cannot recreate in HTML, e.g. have options drop downs that extend outside the viewport boundaries, makes this a really helpful feature. Now, do autocompletes and tag selectors next...
It's actually crazy that we don't have a basic typeahead component or tag selector in this day and age with HTML. Every web page I've ever built has needed these components and while there are libraries out there, they all have an annoying bug here or there. But considering we are just now getting Select tags with styling, signals how long it might take for a typeahead which is vastly more complex.
also drag and drop rearrange
Re: The <select> element can now be customized with CSS
#43> It doesn't trigger built-in mobile operating system components. I worry about this. The built-in mobile operating system components are reliable, accessible, and responsive. I really like it when an input element opens the Android UI because I know how it works and that it is reliable. This applies to , but also date/time inputs for example.
Chrome already uses plenty of non-native components. Firefox is similar. Moreover while I can understand the concern about poorly implemented components from random web developers, Google is probably the best positioned to implement a widget that faithfully replicates the native equivalent, at least on Android.
you're misunderstanding, this will leave the appearance of the select on mobile up to the web developer
Re: The <select> element can now be customized with CSS
#44hey, this is about 20 years late.
Re: The <select> element can now be customized with CSS
#45The fact that I'm disproportionally excited about this probably dates me as an early 2000s web developer. But since selects can do things that you simply cannot recreate in HTML, e.g. have options drop downs that extend outside the viewport boundaries, makes this a really helpful feature. Now, do autocompletes and tag selectors next...
I doubt it'll still be able to do those things. From the article: >Using base-select loses a number of features and behaviors: > The doesn't render outside the browser pane. > It doesn't trigger built-in mobile operating system components. I have mixed feelings about it. Mobile users, get ready for poorly optimized select elements. On the other hand it reduces the need for javascript for styling forms, which is good
That's fair, but I assume that is the initial implementation. Surely, over time, browser vendors will want to make the full spectrum of select functionality available consistently.
Re: The <select> element can now be customized with CSS
#46Some controls are better left unstyled. Look what happened to scrollbars: either they are too thin to grab, have bad color contrast, so it is hard to see what part to actually grab, and, finally, some smartypants have managed even to remove scrollbars altogether from their website. Sure, default select is not the prettiest control, but it gets it job done.
Re: The <select> element can now be customized with CSS
#47Earlier quoted context omitted.
I agree that this is a huge improvement, but it's also over a decade late IMO. This should've been accomplished well before now, especially given that the issue has been there since the beginning.
I somehow feel Safari drags its feet on basic things platform improvements because they want to focus on iOS apps instead.
Eh; the standard is two weeks old. Written by someone working for Apple by the way.
Re: The <select> element can now be customized with CSS
#48Earlier quoted context omitted.
I was just wondering how people do a custom now. I guess they make it screen-reader-only and then have aria-hidden checkboxes for everyone else.
"Select multiple" is just a list of checkboxes. The missing part (which is also missing from select) is just the filtering. I am not holding my breath for a decent "select multiple" field. It's been the same crap for decades and browsers could have fixed it long again without waiting for spec - it's just a "replaced element", but they don't care. The fun part is that it looks amazing on Safari iOS (and QED it's rende…
> "Select multiple" is just a list of checkboxes.
Not necessarily. I've seen more than one production app with a custom filtering dropdown list of items with checkboxes.
I built a couple variants of that in React at my last gig for the company's design system. The keyboard nav was complex... that component is one of the work artifacts that I'm most proud of.
Re: The <select> element can now be customized with CSS
#49Earlier quoted context omitted.
I doubt it'll still be able to do those things. From the article: >Using base-select loses a number of features and behaviors: > The doesn't render outside the browser pane. > It doesn't trigger built-in mobile operating system components. I have mixed feelings about it. Mobile users, get ready for poorly optimized select elements. On the other hand it reduces the need for javascript for styling forms, which is good
That's fair, but I assume that is the initial implementation. Surely, over time, browser vendors will want to make the full spectrum of select functionality available consistently.
I don't think browsers will ever let web code affect things outside the viewport because scammers would cook up some truly zany things with that power.
Re: The <select> element can now be customized with CSS
#50Earlier quoted context omitted.
It's actually crazy that we don't have a basic typeahead component or tag selector in this day and age with HTML. Every web page I've ever built has needed these components and while there are libraries out there, they all have an annoying bug here or there. But considering we are just now getting Select tags with styling, signals how long it might take for a typeahead which is vastly more complex.
> basic typeahead It isn’t perfect, but have you tried ? Totally agree about tag pickers, I was bummed to see that Bootstrap didn’t have a tag selector component either.
I have, and failed.