iiinova — where your digital self keeps evolving

Replying to myself: tooltips aren't visible on keyboard focus, or when using a touch device. Any others?

400

Genuine question, I'm not super aware of the accessibility issues here, can you say what they are?

200

Fancy tooltips that use popover and anchor positioning are great. But sometimes all you need is a trustworthy title HTML attribute for a text-only tooltip. 😭 Only problem is: it can't be styled! Do you want these tooltips to be stylable? Maybe with a ::tooltip pseudo. Let me know your use cases!

A light pink box with the text Hover me inside it. A tooltip is displayed next to it, with the text I'm a sad little tooltip. Please style me.

6313

Patrick Brosset @patrickbrosset.com · 24/09/2026

Anyone can contribute to WPT. If you want to be added to the github org and get write access, I suggest getting in touch with other members via the matrix chat: app.element.io#/room/#wpt:m... and asking there. If you know other people who already have access, that will help.

210

The call for Interop 2027 proposals is closing today. More than 100 proposals got created! Here are my favs 🤩 patrickbrosset.com/lab/interop-... Check them out!

40 colored squares with my favorite feature names.

2218

Reposted by Patrick Brosset

Kevin Powell @kevinpowell.co · 23/09/2026

It's annoying to keep hearing about cool CSS features only to find out browser support isn't great, so today I take a look at a bunch of features that have fantastic support, but people still turn to JS for instead. youtu.be/qu1jE41O_8o

youtu.be

Use these CSS features instead of JavaScript

YouTube video by Kevin Powell

210729

[Image Preview for HTML Images] Do better than blurhash · Issue #1406 · MicrosoftEdge/MSEdgeExplainers

One interesting thread emerged, downstream from the previewsrc attribute: 🔵 Would you use it to display unrecognizable blurs, because they're really small? 🔵 Or would you use it to show more recognizable previews, if you're willing to spend around 10x more bytes? Share your point of view here ⬇️

github.com

Blurhash is cute and nothing else. It's close to useless even compared to CSS features we may soon get. It seems like sites are moving away from it for good reason. For example, I was sent an X lin...

021

No I'm not avoiding it. If we're able to provide something that's representative of the final image immediately, then I'm sure a lot of folks will want this. All I'm saying is that may not everyone. This needs concrete evidence which I don't yet have, either way.

100

Manuel Matuzović @matuzo.at · 23/09/2026

Manuel is a really nice person, and his blog is great. If you've been wanting to do some public writing, I 100% recommend jumping on this opportunity.

030

Reposted by Patrick Brosset

The CFP is open for 10 more days. So far, I have only 11 submissions, but I need at least 24. So, please share your ideas! First-time authors are very welcome!

21118

Making something that would otherwise be empty look nice?

110

Again, I’m not sold on blurhash. I was just defending the mini-blurry-unrecognizable use case. 100%, if we can achieve it with existing platform primitives rather than adding a new image format, sign me up.

Can you share indications of this moving away from blurhash trend? I’m not convinced the 1kB AVIF is always better. I feel like many sites don’t care as much for quick recognition of the image and really just want the smallest thing possible that fills the empty area instantly.

100

Sure, I’m not attached to blurhash itself. I just think that very light, kind of artistic blurry shapes seems desirable to a lot of sites. And no, I don’t have this documented (maybe the team does, will ask), this is based on the large number of sites already doing this today.

100

Thanks for filling. I tend to think that cute gradients that are extremely small (a few bytes) are actually a use case though.

100

Good point. The advantages I see for the previewsrc attribute: * Collocated preview and final image URLs (a little easier to manage) * The attribute gets reflected as a property of the image. * The browser manages error handling, best-effort scheduling, etc.

In my case, I'm very familiar with clicking picture cards, and that's what I usually do. But, there's a big fancy button right there now! Shouldn't I be clicking it?

Same here. I got bitten recently, clicked on the big button after convincing myself that, no Patrick, it's not an ad. And got nowhere near the article.

The idea is that controlling the transition would be done via CSS. Specifically by integrating it with the View Transitions API. So you'd write CSS code to customize the fade/zoom/whatever. Would that work?

100

Support for responsive images are for now considered out of scope for a possible first version. See this paragraph: github.com/MicrosoftEdg... Would this be a deal breaker for your use case?

100