Wasn't it due to poor security? libjxl had notorious bugs that would've on par with webp exploit, if present in browser:
https://security.snyk.io/vuln/?search=libjxl
I remember Project Zero cautioning Google's browser team against adding insecure decoders/encoders.
that's what firefox said, not chrome
Probably why Google implemented their own decoder in Rust
https://developer.chrome.com/blog/jpeg-xl-in-chrome#safety_f...
No, that was not part of the reason the Google Chrome team gave: https://groups.google.com/a/chromium.org/g/blink-dev/c/WjCKc...