Post

rich harris
@rich-harris.dev

if you're using the `interestfor` attribute anywhere, you should know that a bunch of googlers just vandalised your site it looks _atrocious_. leaving aside the merits of the accessibility discussion (github.com/w3c/csswg-dr...), am flabbergasted that it shipped in this state. unbelievably careless

Chris Coyier@chriscoyier.net

Oh snort that happened fast.

Bramus
@bram.us

Correction: this hasn't shipped. It's available behind a feature flag so that you can test things. So no, a bunch of Googlers did not vandalise your site … See this thread for details: bsky.app/profile/bram...

Bramus@bram.us

Maybe one thing to clarify here is that this hasn’t shipped. It is _available for testing_ in Chrome _behind a feature flag_ (the Experimental Web Platform Features flag) so that you, developers, can try it out before we actually ship this (unflagged).

2 reposts2 likes

Bramus
@bram.us

Also: we didn't initially plan this ::interest-button at all, but other browser vendors complained about interest invokers not working on touch devices (should they even?) and this is the compromise we settled on … and it's clear from testing that it's not working, so it's back to the drawing board.

rich harris
@rich-harris.dev

Indeed, turns out I had the flag enabled, so not as bad outcome-wise. But it's still worrisome that an obviously-web-breaking feature wasn't vetoed much sooner IMHO! Glad it's being reconsidered

Tobias Fedder
@tfedder.de

Good question. Should they even? I don't think so. If I wanted a button with a popover that also happens to trigger on hover, I'd build that instead of reaching for interest invokers. Not all features work in every context, they never have, and that's fine. Web authors must take responsibility.

Tobias Fedder
@tfedder.de

We wouldn't add "This paragraph is in light pink" right before a text block just because it happens to be rendered on a grayscale display. Or would we?