When it was removed, no other browser supported JPEG XL, and no other browser had expressed an intent to do it. The last thing the web needs is more image formats with limited support. (Could they even have supported it consistently across platforms due to the iOS limitation on all browsers needing to be implemented on WebKit?)
Apple implementing JPEG XL in Safari changes that. Now it's a format with a real chance of being supported across the whole ecosystem.
> Apple implementing JPEG XL in Safari changes that. Now it's a format with a real chance of being supported across the whole ecosystem.
As I’ve mentioned in other threads, I don’t believe the Chrome team didn’t know Apple was going to implement JPEG XL.
There’s lots of communication between the Chrome and WebKit teams.
It’s going to take more than just Apple shipping JPEG XL to perhaps change Google’s point of view; JPEG XL needs to be seen as a game changer that moves the needle.
Yes, it was true for WebP for like a decade. One of the many issues WebP had. Isn't it good to learn from the mistake of WebP, rather than repeat it?
(AVIF was not supported by all browsers on day 1, obviously, but all the major browsers were governing members of the foundation developing it. So it was much more clear that the backing was there across the ecosystem.)
Apple implementing JPEG XL in Safari changes that. Now it's a format with a real chance of being supported across the whole ecosystem.