3 ms·

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/submi

by culi 10mo ago

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-2026/ 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 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 https://github.com/web-platform-tests/interop/issues/994

F3nd0 10mo ago
It took Mozilla two years to decide they were 'neutral', citing a range of vague considerations. It took them another year to say that actually their 'primary concern has long been the increased attack surface of the reference decoder', without pointing out any specific major security flaws, and that they're okay with an implementation in Rust… which had already been proposed by the JXL team many months ago. And let's not even talk about Chrome. Hopefully they've both finally settled on a reasoning and will stick with it until the end.
- culi 10mo ago
  Yeah I guess I wasn't following that closely but I know their previous position was that there wasn't enough benefits to .jxl to justify supporting another raster image standard. There's been a lot of major changes since then though. Like Apple fully adopting JPEG XL and PDF announcing support as well. I know many in the industry also think that AV2 might be a huge game changer and wanna wait and see how that ends up before choosing what standards to adopt.

by culi 10mo ago

F3nd0 10mo ago

It took Mozilla two years to decide they were 'neutral', citing a range of vague considerations. It took them another year to say that actually their 'primary concern has long been the increased attack surface of the reference decoder', without pointing out any specific major security flaws, and that they're okay with an implementation in Rust… which had already been proposed by the JXL team many months ago. And let's not even talk about Chrome. Hopefully they've both finally settled on a reasoning and will stick with it until the end.

culi 10mo ago
Yeah I guess I wasn't following that closely but I know their previous position was that there wasn't enough benefits to .jxl to justify supporting another raster image standard. There's been a lot of major changes since then though. Like Apple fully adopting JPEG XL and PDF announcing support as well. I know many in the industry also think that AV2 might be a huge game changer and wanna wait and see how that ends up before choosing what standards to adopt.