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

171–180 of 194 posts

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

#171

Post by codedokode »

tredre3 wrote: post #134
codedokode wrote: post #122

Earlier quoted context omitted.

Firefox doesn't have ad measurement and interests sharing built in yet (or am I wrong?) so it is very relevant for me. I would rather use black-and-white selects everywhere rather than having an advertising engine built into the browser.

You are indeed wrong. https://support.mozilla.org/en-US/kb/privacy-preserving-attr...

That is disappointing. I went into settings to turn this off but it is already turned off and I don't remember whether I did it or my distribution ships Firefox with non-recommended settings. I hope it is the latter so that I don't get disappointed in Linux distributions also.

"Privacy preserving attribution" sounds like "money preserving robbery" (or money preserving tax).

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

#172

Post by porridgeraisin »

hbroadbent wrote: post #166
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...

The rule is:

Styleable XOR Unusable = 1.

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

#174

Post by vntok »

blatantly wrote: post #96

> Changes the browsers HTML parser Sounds like you can create loops. If the select had a style element that turns this off again would it keep changing state?

I don't see how it would create a loop? It seems like the parser change only impacts 's descendant elements (to stop "cleaning" them of illegal elements), not itself.

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

#175

Post by jeffhuys »

hk1337 wrote: post #71

meh. it looks really nice but I would rather do the basic styling I can do now for the 99% of the times where I don't really need it. I have said it before, everyone (Developers that use Chrome almost exclusively) says Safari is the new IE but Chrome has been slowing becoming the thing they fought against since they defeated IE.

I'm sitting here for a few years already, happily using Safari as my main driver. Recently switched to Orion to get Safari + Chrome/FF plugins. Best combination.

Easy on the battery, freaking fast, low ram usage, and plugin support (ALSO on iOS, yes, uBlock on iOS). Screw firefox, screw chrome.

Yes, I also dev on Orion. The dev tools are fine.

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

#177

Post by mason55 »

progmetaldev wrote: post #130
sublinear wrote: post #118

Earlier quoted context omitted.

ISO-8601 is not the correct format for serializing local time unless it's in the past. In my experience, a local datetime picker is going to be used almost exclusively for a future date and time. What you want instead of a timezone offset is a zone ID. That way date and tzdata can handle it properly on the backend.

For this case, I will often ask for the timezone, since that data is often updated on the operating system, but I don't believe it's often for someone to be in the same location and have their timezone change. The software that I've maintained the most over the years (since 2009 up to deploying an update today) requires a login, so I have a client account that includes choosing their timezone. I then use that to conv…

This works for things in the past but not things in the future.

If I say I want something to happen at 8pm New York City time on January 7, 2028 and then the DST rules for NYC change, I likely still want it to happen at 8pm. Converting to UTC and back to local time loses that information and it will happen at the wrong time.

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

#178

Post by klysm »

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 might be a bad take, but I think developers should also consider exactly which users are using their app. If it’s the entire internet, then absolutely you need to consider backwards compatibility. If it’s an internal app, then consider not caring and using new APIs.

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

#179

Post by hk1337 »

jeffhuys wrote: post #175
hk1337 wrote: post #71

meh. it looks really nice but I would rather do the basic styling I can do now for the 99% of the times where I don't really need it. I have said it before, everyone (Developers that use Chrome almost exclusively) says Safari is the new IE but Chrome has been slowing becoming the thing they fought against since they defeated IE.

I'm sitting here for a few years already, happily using Safari as my main driver. Recently switched to Orion to get Safari + Chrome/FF plugins. Best combination. Easy on the battery, freaking fast, low ram usage, and plugin support (ALSO on iOS, yes, uBlock on iOS). Screw firefox, screw chrome. Yes, I also dev on Orion. The dev tools are fine.

One of the main features I love about Safari is that in private browsing mode, the tabs (at least) appear to be completely isolated.

If I go to Facebook and login in one tab, then open a second tab and go Facebook, it doesn't recognize that I have logged in. There's moments where that is annoying but most of the time it's useful.

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

#180

Post by jeffhuys »

hk1337 wrote: post #179
jeffhuys wrote: post #175

Earlier quoted context omitted.

I'm sitting here for a few years already, happily using Safari as my main driver. Recently switched to Orion to get Safari + Chrome/FF plugins. Best combination. Easy on the battery, freaking fast, low ram usage, and plugin support (ALSO on iOS, yes, uBlock on iOS). Screw firefox, screw chrome. Yes, I also dev on Orion. The dev tools are fine.

One of the main features I love about Safari is that in private browsing mode, the tabs (at least) appear to be completely isolated. If I go to Facebook and login in one tab, then open a second tab and go Facebook, it doesn't recognize that I have logged in. There's moments where that is annoying but most of the time it's useful.

Yeah they are, which is IMO a good thing but it'd be better if you could link them somehow, maybe have a temporary session or something.
Post reply on HN