I see some nice activity there on the Mozilla bugtracker for an implementation of `hidden=until-found` 😍

https://bugzilla.mozilla.org/show_bug.cgi?id=1761043

@Kilian It is also a lot more convenient than Chrome's local override feature and it would go hand-in-hand with Polypane's ability to disable CSP and CORS checks (for which I also needed separate extension, which are now also broken with Manifest V3)

@Kilian I do have a feature wish for Polypane:

Would it be possible to re-implement what the Chrome/FF extension "Resource Override" offered in the past, being that you could define URL patterns for website resources, which you could then remap to another URL or a local file e.g. https://polypane.app/**/*.js -> http://localhost:3000/**/*.js

I use that a lot to develop frontend-code, applying + checking it with the live-site, w/o having to run it via Docker locally.

👉 https://addons.mozilla.org/en-US/firefox/addon/resourceoverride/

@marcozehe @svenja

Hey Ihr beiden! Gerade erreichte mich seitens @spittank folgende Frage zu meinem Post zur Verbesserung von "Find-in-Page" wie im vorherigen Toot verlinkt:

"Sehr spannender Ansatz!
Mich würde interessieren, wie gut das in der Praxis für Screenreader Nutzer funktioniert. Wenn ich damit teste fühle ich mich immer komplett überfordert."

Wie ist Eure Meinung zu "Find-in-Page" generell und zur Idee, Icon-Links oder Icon-Buttons per `hidden="until-found"` auffindbar zu machen?

Hey Rotterdam! Next week, March 4th, @fronteers teams up with Level Level to host a meetup. There will be talks about accessibility barriers in e-commerce & how embracing the web platform's native strengths is key to a solid design system. And there's still plenty of seats left! 👇

https://www.meetup.com/fronteers-nl/events/306217952/