It's a new addition as part of the parser and content model updates for customisable select. I don't have a demo to hand unfortunately.

They should be styleable too, you can even use <legend> to provide a styleable override the optgroup's label attribute.

Likewise! I'll also be at state of the browser in February if you're about.

Just bought my ticket, my first and last time there. Hard to argue when like 6 people on my timeline all share and go BUY.

Would be potentially useful for type inference too, especially with the conditions after a ;

I think the UX 'issue' of the arrow keys still apply, if you're genuinely entering a number I think it's fine (not sure about dragon natural speak support), but if it's just something numeric then I think their suggestion still applies.

It's in Safari 18.2 (current beta)

I'm a professional browser engineer, I know CSS I promise... (It's child elements that the & is optional for?)

Great photo! Is that from earlier this year, or are they there now?

...so far they've all failed to do that, many don't even have proper browser level settings let alone site settings. So in lieu of / alongside that a JS API would be nice.

It's made it into the CSS media queries 5 draft. Mostly just needs someone with time to help drive it a bit. There's a partial implementation in chromium for those that want to try it (doesn't persist settings yet though). But yes the idea is that browsers could provide UI for this, but...

Isn't this already a thing?

input:hover {
::file-selector-button {
}
}

Well it is open source you know, go contribute 😉

Definitely won't take you a week to compile chrome!

Chrome deprecated and spec deprecated are different though so I think that's why most things don't log anything.

Suddenly devtools is riddled with console warnings! 😂 But yes I agree, tbh it'd be nice to have a strict mode in Dev tools that drops these from the prototype to stop you using them...

That's why it's "deprecated" and called target now 😂