File an issue against whatwg/dom and we can explore. I’d imagine @lcas.dev and @nicr.dev to have thoughts about this.

Congratulations! Hope this means I’ll see you at TPAC. Does this mean @surma.dev will soon return to the web platform as well? 😊

Yes, you can do this:

<input type=color list=x><datalist id=x><option value=red><option value=blue></datalist>

There have been some requests for exposing the color as an object to JavaScript. Filing an issue against the HTML standard for alternate serialization formats seems reasonable.

Thanks to @jensimmons.bsky.social for significantly improving the above post; @patrickangle.net, @smfr.bsky.social, and Aditya for design feedback; Chris Lilley for improving the relevant CSS standards; and @domenic.me for helping out on the HTML side and filing the initial issue.

I don’t see the relationship. Even if we had discovered it earlier, it would still lead to a lesser web standard. Literally doesn’t matter. The act of polyfilling is what is problematic. Not when we discover somebody did it.

I'll try to rephrase as all of this is besides the point I was trying to make. Which is that the polyfill (and others like it) limit the options we have in the design space. The end result is lesser web standards for everyone.

No, ‪Nicolò understood it correctly.

I’m not sure how they help with this particular problem.

Please describe why you and end users would want this behavior in the issue. The more compelling the story, the more likely you’ll nerd-snipe someone into fixing it.