Consider proposing jxl-oxide to Firefox as an alternative solution for adding JPEG-XL support

[Kaleidosium]

Recently, Firefox has indicated that they are open to implementing JPEG-XL support in Firefox if there is a memory-safe Rust implementation of JPEG-XL. They're betting on the team at Google to create an implementation that satisfies their requirements.

However, in the event of them not being able to do it (or being forbidden to do it by upper-management, since y'know), I'd like to see jxl-oxide being brought up as an alternative solution for adding JPEG-XL support in Firefox. Is the library stable enough to be proposed as a solution, or is more work needed?

[tirr-c]

I'm in contact with some of the core devs in the JPEG XL community Discord server, and whether to use jxl-oxide as a base for the support in Firefox is yet to be decided (more work is needed, especially to match performance requirements, at least).

[mlindner]

Perhaps a dumb question, but when you say more work is needed, do you mean within jxl-oxide? If so, is there sufficient information to create issues so that people can submit pull requests?

[tirr-c]

Perhaps a dumb question, but when you say more work is needed, do you mean within jxl-oxide?

Yep.

If so, is there sufficient information to create issues so that people can submit pull requests?

#336 and #337 can be done without knowledge on JPEG XL bitstream (I think). A challenging one is #239; this requires understandings on how spline rendering is defined by the spec.