Firefox 157 will include JPEG XL by default on all platforms

Timothy Nikkel

unread,

As of Firefox 157 I intend to move JPEG XL decoding connected by default connected each platforms. It has been developed down image.jxl.enabled, which coming is connected by default connected Nightly only, and has had a Firefox Labs checkbox connected each transmission since 152. The decoder is jxl-rs, successful Rust.

Bug to move connected by default: https://bugzilla.mozilla.org/show_bug.cgi?id=2065096

Standard: ISO/IEC 18181, https://www.iso.org/standard/85066.html

Standards body: ISO/IEC

Platform coverage: all

Preference: image.jxl.enabled

Standards position: https://github.com/mozilla/standards-positions/issues/522 (neutral)

TAG review: https://github.com/w3ctag/design-reviews/issues/633 (satisfied pinch concerns)

Intent to prototype: https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/53b4e3e0-5eee-4768-a1ba-b069e1e85244n%40mozilla.org

Other browsers: Safari shipped successful 17.0 successful 2023. Chrome has it down #enable-jxl-image-format utilizing the aforesaid Rust library, nary intent to vessel yet.

Changes since the intent to prototype:

Performance was a interest raised connected the intent to prototype thread. jxl-rs 0.6.0 was released pinch multithreaded decoding support, and our patches to hook up and alteration multithreaded decoding are expected to onshore soon. Including those patches, I ran a five-format decode benchmark complete the aforesaid pictures astatine a scope of sizes: we were somewhat up of Safari (using C++ libjxl) connected my machine. Compared to our different image format decoders, JXL is adjacent connected ample images, but shows a bigger spread connected mini ones.

It has characteristic parity pinch our different image formats and pinch Blink's JXL implementation, including animation and progressive display. The 1 objection is HDR: HDR images show arsenic SDR, the aforesaid arsenic each different format we support, but our reside mapping for JXL is overmuch amended than what we do for different image formats. Safari has neither progressive rendering nor animation.

The wpt jpegxl directory covers decode correctness crossed spot depths, alpha, grayscale, CMYK, colour management, predisposition and the coding tools, positive the HTML and CSS ways an image gets used. Where wpt could not definitive thing I added gecko tests: astir 30 gtests for chunked and incremental decoding, animation framework counts, downscale during decode and corrupt files, mochitests for progressive rendering and telemetry, reftests, and decode benchmarks that study to Perfherder. The fuzzing squad already fuzzed jxl earlier it was enabled connected nightly and they will fuzz the decoder again earlier I flip the pref.

Timothy Nikkel

Timothy Nikkel

unread,

一丝

unread,

Timothy Nikkel

unread,

Yes. Animated jxl is supported.

Tim

Sergey Davidoff

unread,

$ hyperfine --warmup 5 'taskset -c 0 target/release/jxl_cli --speedtest 55_Cancri_e_Final_1_30.jxl' 'taskset -c 0 dwebp 55_Cancri_e_Final_1_30.png.webp'
    Benchmark 1: taskset -c 0 target/release/jxl_cli --speedtest 55_Cancri_e_Final_1_30.jxl
      Time (mean ± σ):     20.632 s ±  0.061 s    [User: 20.605 s, System: 0.027 s]
      Range (min … max):   20.549 s … 20.743 s    10 runs
     
    Benchmark 2: taskset -c 0 dwebp 55_Cancri_e_Final_1_30.png.webp
      Time (mean ± σ):     667.0 sclerosis ±   2.2 sclerosis    [User: 449.5 ms, System: 217.5 ms]
      Range (min … max):   664.3 sclerosis … 670.1 sclerosis    10 runs
     
    Summary
      taskset -c 0 dwebp 55_Cancri_e_Final_1_30.png.webp ran
       30.93 ± 0.14 times faster than taskset -c 0 target/release/jxl_cli --speedtest 55_Cancri_e_Final_1_30.jxl