4 ms·
Disappointing. I'll have to figure out the JXL WASM polyfill. Maybe if I wait a few months someone else will do it for me? There's https://github.com/GoogleChr
by Scaevolus 4y ago
Disappointing. I'll have to figure out the JXL WASM polyfill. Maybe if I wait a few months someone else will do it for me?
There's https://github.com/GoogleChromeLabs/squoosh/tree/dev/codecs/jxl/dec https://github.com/GoogleChromeLabs/squoosh/tree/dev/codecs/... that provides `JXLModule.decode(data: BufferSource): ImageData | null`, but for a polyfill I suspect you'd want a method to get the dimensions of the image and an IntersectionObserver to defer actually decoding the image until it scrolls into view. Having to load the image with XHR is annoying.
- Gigachad 4y agoIf hardware decoding support wasn't going to happen, is there really any problem with a polyfill since presumably the performance would be similar? I suppose if it's just one image, the weight of the polyfill download may make the savings in image compression worthless.
- JyrkiAlakuijala 4y agoseveral wasm solutions will soon appear in libjxl github