Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The element can now be customized with CSS

developer.chrome.com

Post reply on HN
Print view View original

161–170 of 194 posts

Re: The <select> element can now be customized with CSS

#161

Post by pests »

no_wizard wrote: post #109
pests wrote: post #100

Earlier quoted context omitted.

In the original dev blog from last year they mention it’s still a work in progress. https://developer.chrome.com/blog/rfc-customizable-select > Note: The multiple and size attributes on select ( and ) are not supported in appearance: base-select yet.

From last year while it was a WIP and now this as of Chrome 135 is shipped, and they didn't think it wise to include a back reference to this post, calling out what isn't supported? They can and should communicate this is all.

Agreed. Should have mentioned it in this post or at least linked back to my source.

Re: The <select> element can now be customized with CSS

#162

Post by robin_reala »

chias wrote: post #27

The element can now be customized with CSS *in Chromium browsers*

It’s the web equivalent of the Twitter account that added “in mice” to medical headlines. Nice in theory, but it’ll take years before it’s usable and in all likelihood it’s just another experiment that’ll never go anywhere.

Re: The <select> element can now be customized with CSS

#163

Post by true_religion »

alwillis wrote: post #145
true_religion wrote: post #30

Earlier quoted context omitted.

I somehow feel Safari drags its feet on basic things platform improvements because they want to focus on iOS apps instead.

The narrative Safari is behind and Apple doesn’t care about the web is so tired… This 8,000+ word article on Safari 18.4 (released today, BTW) doesn’t read like an organization that doesn’t care about the web [1]. [1]: https://webkit.org/blog/16574/webkit-features-in-safari-18-4...

The pace of improvement in the web is slow.

I don’t want to debate if a mega corp cares or not, but compared to how UI frameworks were in the 90s, the developer experience is anemic.

I don’t know if HTML, CSS and JavaScript are the best path forward. Maybe they are doing exactly what their spec set out to do.

But we need something better that doesn’t leash one to an ecosystem that takes 30% of your revenue.

Re: The <select> element can now be customized with CSS

#164

Post by true_religion »

arp242 wrote: post #47
true_religion wrote: post #30

Earlier quoted context omitted.

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.

I’m wondering where in my comment it sounded like I wanted this standard specially to be implemented yesterday?

Re: The <select> element can now be customized with CSS

#166

Post by hbroadbent »

paradox460 wrote: post #165

I still wish it would grow some primitive filtering/searching feature. I'm very tired of having to reach for JavaScript just to let users narrow a massive list of things

Hey! Actually that is possible using the element.

If you're interested, I wrote a bit more about it here: https://harrisonbroadbent.com/blog/cool-native-html-elements...

Re: The <select> element can now be customized with CSS

#167

Post by Cthulhu_ »

ddoolin wrote: post #24
ljoshua wrote: post #3

The challenge till this is widely supported (caniuse.com currently pegs it at 46% globally [1]) will be using this as a progressive enhancement that does not provide a worse or unusable experience for users with browsers not supporting it yet. In other words, don’t include critical information or functionality in the new styling that isn’t available in the underlying plain select element! But such is always a good pr…

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.

It's like how border-radius was added after rounded corners via images fell out of fashion.

Re: The <select> element can now be customized with CSS

#168

Post by earcar »

Fascinating timing for this feature. I suspect the AI chatbot explosion has been a major driver behind the push for richer select elements.

Have you noticed how every AI interface needs to let you choose between models? The current select element is embarrassingly inadequate when you need to show more than just text labels. You want to display model capabilities, performance indicators, context sizes - not just "GPT-4" vs "Claude 3.7" as plain text.

Re: The <select> element can now be customized with CSS

#169

Post by lelanthran »

tracker1 wrote: post #110
no_wizard wrote: post #107

Earlier quoted context omitted.

There's some quirks with the API around open vs openModal if you aren't aware of the accessibility implications you may not even realize this is the case. Forms have some special quirks inside of a dialog. The biggest thing though, is for the life of me I don't understand why you can't open and close a dialog without JavaScript. There's no way to do it.

I'm with you... would be nice to have: Open Dialog ... Close Dialog It would just make so much sense.

> I'm with you... would be nice to have:

You can do this right now already:

    // For  opening
    Open

    // For closing
    Close
I think the problem here is that it is impossible to actually use the result from `close()`, as it can return a status, IIRC.

> It would just make so much sense.

That way above that I propose is about as sensible as the way you propose. If there are any problems with my proposal that are solved by your proposal, I'd love to hear it.

Re: The <select> element can now be customized with CSS

#170

Post by porridgeraisin »

kkarpkkarp wrote: post #68
wolframhempel wrote: post #36

The 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...

> Now, do autocompletes This is kind of ready, see datalist element. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/da...

I know about datalist, but it's the saddest autocomplete experience you can offer. If something is not fully styleable, it's automatically garbage. If it's styleable, it may be decent.

Now, I understand why datalist is not styleable the way it is implemented right now. On Android, the suggestions come on the top bar of the native keyboard, so it doesn't make sense to be able to put arbitrary divs there. But in that case, there should be an alternative styleable autocomplete element.

Another element that is unstyleable crap is , too.

Post reply on HN