Chrome Responds "No" to JPEG XL

Re:Chrome Responds "No" to JPEG XL by gjsman-1000 on Friday November 11, 2022 @12:40PM (#33563934)

Well... within the last ~1.5 years, AVIF has become natively supported on Windows 10 and Windows 11 (Windows 1903 with a free Store extension), macOS 13 (no AV1, but yes to AVIF), iOS 16 (no AV1, also yes to AVIF), and Android 12. And in browsers, AVIF won Firefox, Safari, and Chrome all together as a default supported option, JXL did not and was only an optional feature flag in Firefox.

Basically, AVIF won the OS-level support race by a landslide. JXL hasn't taken any victories in OS-level support yet. With the winner increasingly becoming obvious, time to cut the losses on JXL and run.

Part of this may be as well that AVIF is basically just an AV1 still. If you implement AV1, you've got 95% of your AVIF support already done.

[ Parent | on HN ]

Re:Chrome Responds "No" to JPEG XL by jonsneyers on Friday November 11, 2022 @12:52PM (#33564121)

Note a small detail you left out: all this happened to AVIF _after_ it was enabled by default in Chrome...

[ Parent | on HN ]

Re:Chrome Responds "No" to JPEG XL by erk__ on Friday November 11, 2022 @01:33PM (#33564759)

I don't think AVIF was ever behind a flag in Chrome, it was always enabled by default as long as it have been a part of it.

[ Parent | on HN ]

Re:Chrome Responds "No" to JPEG XL by jonsneyers on Friday November 11, 2022 @01:41PM (#33564872)

Correct. Same for WebP. Both were enabled before their specs were even finalized.

[ Parent | on HN ]