If you have existential feelings about the state of your software stack, just remember that on the web it’s completely undefined which element a mouse click returns.
27.01.2026 14:17
👍 9
🔁 2
💬 3
📌 0
If you have existential feelings about the state of your software stack, just remember that on the web it’s completely undefined which element a mouse click returns.
Evergreen sentiment. (If you always wanted to be a specification editor, wiki.whatwg.org/wiki/Specs/t... has some suggestions. Most still relevant.)
Web component folks: A common feature with request is to "inherit from a button". If that's something you want, which specific button behaviours is it you want to inherit? Why is putting a button in the shadow root not the answer?
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? 😊
I work as an elder and hospice caregiver, which I am oddly passionate about. I can love on them shamelessly and no one complains about my codependence. It's a win-win situation. Many of my caregiving colleagues complain about the repetitive questions and, sometimes reactions, of the elderly, especially when those patients happen to read the newspaper, especially with the current downward spiral of our country — as if these people haven't lived through enough horror... I love my dementia peeps, but sometimes wonder if there's a Guinness Book World Record for how many times an hour a dementia patient can repeat the same question — it's got to be in the hundreds. At least with small children, they ask different questions. Dementia patients will get stuck on one short question and ask it until you can interrupt their train(carousel) of thought and successfully redirect their attention. That carousel is pretty manic sometimes. A couple days ago, I picked up my mail from the post office and drove over to the nursing home to take (let's call her "Miss Daisy") Miss Daisy out for a drive. Before we took off on our road trip, to the end of The Road and back, in our landlocked little town (Juneau, Alaska), I set my copy of The Onion down in front of her. Over our two-hour excursion, tiny Miss Daisy read that front page at least a dozen times and each time she would snicker, giggle, and guffaw, then put it down on the dash board and, a minute later, discover it anew. I think it was the best afternoon of my life. We don't often hear them laugh and when they do, it's the sweetest thing you've ever heard. ... Thank you, thank you, thank you, for the really important work all of you do. You make the world a better place.
I got permission to share this, and I'm extremely grateful for that.
The Onion got this letter from one of our subscribers in Alaska. She works with dementia patients and decided to leave a copy in the car for each one.
This email made my year. Read it and you'll see what I mean. People are good.
APNG finally graduated from its MozillaWiki documentation to a proper standard: www.programmax.net/articles/png...
If you want to learn more about Declarative Web Push or Web Push in general, my colleague Brady put out a great video: developer.apple.com/videos/play/...
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.
🥳 We added new attributes to HTML to enhance <input type=color>: webkit.org/blog/16900/p...
If you write code to make websites (HTML, CSS, JS, Web API, Media) and you get frustrated trying to wrangle your code to work in Safari, which bugs are blocking you? Which existing features would you most like to see improved? If you got a chance to order priorities which effort would you put first?
Please don't publish / release a polyfill for unshipped Web features. Someone is bound to use it in production and ruin it for everyone else.
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.
And yet another polyfill appears to have poisoned the standards well. This time for scoped custom element registries. People never learn. 🫠
I have at times told people that if you want to generate XML, you should use a serializer. So when I had to generate a serialized CSS URL value containing a data: URL of an SVG document of which colors could vary, I immediately went for string manipulation and concatenation. 😅
📅 Save the dates! The Web Engines Hackfest 2025 will take place June 2-4 in A Coruña, Galicia (Spain).
Check more details at: webengineshackfest.org
The aliens are coming and their goal is to invade and destroy Earth.
Almost time to sign off for the year. Web standard proposals to finish in (early?) 2025:
- Declarative Web Push
- Scoped Custom Element Registries
- HTML (and SVG & MathML) Sanitizer API
- moveBefore()
- fetchLater()
- float16 in 2D canvas
- <button command>
and quite a few more. Happy holidays!
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.
git blame as visualized by GitHub (or Searchfox for the HTML standard) is an amazing development tool for projects that span decades. In particular for projects that enforce good commit messages. Being able to answer why something is the way it is, can be crucial when changing it.
@annevk.nl and I worked on a refined proposal to untie scoped element registry from shadow DOM so that you can use a scoped registry without shadow DOM. Your feedback is appreciated:
github.com/whatwg/html/...
Not having to observe mutations is an improvement I’d say! They’re very costly.
FWIW, it looks like the Chromium fix is incorrect (aside from being inelegant). It doesn't work for custom element callbacks.
Unfortunately I didn’t see this earlier. Curious to see how your fix compares to mine: github.com/WebKit/WebKi...
There is? I assume you mean why there is no API? See github.com/whatwg/url/i...
The only thing I know is that Service Workers and Compression Dictionary Transport use a subset of the full API for this reason. For routing I would imagine you would have to do something similar. @ssd.bsky.social and @wanderview.com can better speak to this I suspect.