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

21–30 of 194 posts

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

#21

Post by no_wizard »

dqv wrote: post #9
dpcx wrote: post #5

This looks like what web developers have been waiting literally decades for. Possibly replacing (eventually) a bunch of JS libraries to make this all do what we want. I don't have Chrome installed, but I'm curious how it handles multi-select fields, as I didn't see that in the example video.

I just tried it in the Codepen and it reverts to a regular old UI element when it has the multiple attribute. Also just tried it with multiple="multiple" just in case. Same behavior.

Huge miss in my opinion. If it doesn’t support all scenarios I’m not sure what the Chrome team is thinking here

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

#22

Post by paddy_m »

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…

This is true, and I try not to get eager about new browser improvements for this reason. But look at the porgress over time in browser abilities, it's astounding.

The days are long but the years are short.

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

#23

Post by simiones »

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…

You'll probably still keep a -based control in your page, and selectively hide the based one or this one, or generate different HTML for different browsers if you can do that.

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

#24

Post by ddoolin »

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.

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

#26

Post by pclmulqdq »

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.

Because frontend is frontend, Javascript frameworks dominated the conversation even for silly things like basic web forms for the past 15 years. Basic HTML/CSS is now catching up to the fact that not everyone wants to run a Javascript monstrosity for custom styling on very basic tasks.

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

#28

Post by dqv »

no_wizard wrote: post #21
dqv wrote: post #9

Earlier quoted context omitted.

I just tried it in the Codepen and it reverts to a regular old UI element when it has the multiple attribute. Also just tried it with multiple="multiple" just in case. Same behavior.

Huge miss in my opinion. If it doesn’t support all scenarios I’m not sure what the Chrome team is thinking here

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.

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

#29

Post by [deleted] »

pclmulqdq wrote: post #26
ddoolin wrote: post #24

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

Because frontend is frontend, Javascript frameworks dominated the conversation even for silly things like basic web forms for the past 15 years. Basic HTML/CSS is now catching up to the fact that not everyone wants to run a Javascript monstrosity for custom styling on very basic tasks.

[deleted]

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

#30

Post by true_religion »

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.

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