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

31–40 of 194 posts

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

#31

Post by no_wizard »

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.

The prevalence of JS and JS backed components is due to the reluctance of browser vendors to introduce new HTML elements that everyone has been lobbying for in the same time period.

By and large browser vendors for the longest time, even today still in many respects, repeatedly ignore pleas for more elements that cover common use cases.

Even when they do arrive, they can be half baked - like dialog or details / summary - and that doesn’t help matters

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

#32

Post by pests »

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

Incremental improvement?

Why release anything right?

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

#33

Post by zb3 »

Developers, don't fall for this!

This web API scope creep makes it __harder__ to create and maintain truly independent web browsers.. you have to implement more and more and eventually we arrive at the current state of matters - all non-chromium engines are lagging behind.

Developers will happily use this, then users will notice websites "look better" in chrome and firefox will become even less relevant. Don't.. you can already achieve this without relying on chromium-only APIs.

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

#34

Post by sureIy »

dqv wrote: post #28
no_wizard wrote: post #21

Earlier quoted context omitted.

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.

"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 rendered as a list of checkboxes)

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

#35

Post by gjsman-1000 »

zb3 wrote: post #33

Developers, don't fall for this! This web API scope creep makes it __harder__ to create and maintain truly independent web browsers.. you have to implement more and more and eventually we arrive at the current state of matters - all non-chromium engines are lagging behind. Developers will happily use this, then users will notice websites "look better" in chrome and firefox will become even less relevant. Don't.. you…

> and firefox will become even less relevant

No; Firefox can easily afford financially to add this feature. Firefox is already irrelevant; no developer will shed a tear about just blocking Firefox if they refuse to implement. Boycotting won't work either, because boycotts almost never work.

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

#36

Post by wolframhempel »

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

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

#37

Post by majora2007 »

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

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.

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

#38

Post by jhardy54 »

majora2007 wrote: post #37
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...

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.

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

#39

Post by renerick »

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

> have options drop downs that extend outside the viewport boundaries

Unless this is about something different from what you mean, unfortunately, it's not the case, as stated in the article:

> Using base-select loses a number of features and behaviors:

> The doesn't render outside the browser pane.

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

#40

Post by asddubs »

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

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

Post reply on HN