interop

https://github.com/web-platform-tests/interop/. But… yeah, they should be on the site even before you log in. Let me fix that… Fixed! Thanks for the suggestion. There was a whole read-only mode already there for when the process closes. I just didn't think of using it when the user is logged out.

That’s not at all how it went. Years ago, both Chrome and Firefox had experimental support. In October 2022, Chrome suddenly announced their decision to drop it (citing dubious reasons like lack of interest or improvements over existing formats). [1] It was only later, in January 2023, that Mozilla announced their formal position of not really caring about the format. [2] In October 2023, one of the JPEG XL devs said that the responsible team at Google was ready to write a decoder in Rust if that was the only reason holding adoption back, even offering to work on browser integration. [3] One month later, another dev confirmed that a different pre-existing decoder written in Rust was already standard-conformant. [4] It wasn’t until September 2024, nearly a whole year later, that Mozilla changed their official position from not caring to wa

> Your premise that the browser implementation is faster and better is rarely true Thankfully, this opinion is measurably false just by reviewing source code of any website. What you're referring to, primarily, are categories of elements like form elements like <datalist> and that's fair. This is why the web community is asked to support improving the platform through submissions to Interop, such as this one for <datalist> https://github.com/web-platform-tests/interop/issues/1402

Yes. They're adding it back to Chrome. This last January at FOSDEM there was a panel with representatives from different browser companies. During the panel Kadir Topal, a web platform product manager at Google, indicated that because of the interest they saw in JPEG XL through the Interop Project that they changed their course on supporting it. https://github.com/web-platform-tests/interop The video of the panel can be found at https://fosdem.org/2026/schedule/event/7E7387-browser_in_202... . He starts speaking on the issue at about 13:00

Yes exactly. Voting for the 2026 focus areas is happening now btw. The next year's interop usually releases around February https://webkit.org/blog/17320/submit-your-ideas-for-interop-... And yes JPEG XL support is often the most requested feature and the major browsers have responded. Google and Firefox are both willing to take it on but Firefox's biggest concern is with the reference decoder which has some major security flaws. They basically want to wait until libjxl/jxl-rs is performant enough https://github.com/mozilla/standards-positions/pull/1064 Here's the current issue for that proposal if you want to get involved https://github.com/web-platform-tests/interop/issues/994

voting for interop 2026 is active now. I see somebody has already submitted a proposal for it https://github.com/web-platform-tests/interop/issues/1121

Far from being ready when only one major browser supports it. If you want this, you should vote for it to be focused on for interop-2026 https://github.com/web-platform-tests/interop/issues Right now, the leading CSS proposals are `@container style()`, `corner-shape` and `break-after` https://foolip.github.io/interop-reactions/

Not just Firefox. Safari doesn't have it either. Not usable in a professional context. I've been following the bugzilla issue for it for years now but there hasn't been any real progress on it. I don't think it'll happen until we can get it to an interop.[0] Speaking of which, interop 2026 is still taking suggestions[1] and I don't see any proposal for these inputs [0] https://wpt.fyi/interop-2025 [1] https://github.com/web-platform-tests/interop/issues?q=is%3A...

I would also add: - Install Prompts / Discoverability - Bugs (like https://github.com/web-platform-tests/interop/issues/84) which likely would only get fixed if Safari has heavy competition on iOS (it's a funding issue)

Well, the drama has some new development as of 2 days ago: https://github.com/web-platform-tests/interop/issues/700#iss...

There is popular demand (including from Adobe https://github.com/web-platform-tests/interop/issues/430#iss..., https://crbug.com/40168998#comment62), which is arguably evidence against (2). (Disclaimer: I’m a JPEG XL contributor.)

> If having a high quality Rust decoder implementation would arise as the only gating factor for choosing JPEG XL into interop 2024, the JPEG XL developer team in Google Research can deliver such by the end of Q2 2024 > We have tested conformance of the jxl-oxide decoder (which is implemented in Rust) and it is a fully conforming alternative implementation of JPEG XL. It correctly decodes all conformance test bitstreams and passes the conformance thresholds described in ISO/IEC 18181-3. https://github.com/web-platform-tests/interop/issues/430