Google has reinstated support for the JPEG XL image format in the open source Chromium code base, reversing a decision it made in 2022 to remove it.
The update allows Chromium to recognize, decode, and render JPEG XL images directly, without extensions or external components.
This change applies at the browser engine level, meaning it will affect future versions of Google Chrome and other Chromium-based browsers when they are released.
I find it funny that just couple weeks ago I’ve written about the format. What’s especially interesting about this format is that it can losslessly transcode JPEG into JPEG XL while offering around 20% file size reduction. It can be used to reduce size of one’s image gallery without any loss of quality.
This is really good news. Everything should be moving to jxl, and browser support is essential for it.
Indeed jpegxl appears to be much better than AVIF. By the way two small questions related to images on Lemmy this probably isn’t the right place but I just remembered it
-
In the browser client you make it possible to paste images into the thumbnail field when creating a post? I saw this functionality added to the Jerboa client recently, it’s pretty useful for when the scraper doesn’t automatically find a thumbnail in a link
-
On lemmy.ml there’s a filesize limit to uploading images in the post field. I often have to manually downsize them to fit the size limit. Would it be possible to automatically encode the images client side when uploading? Maybe make them even smaller when uploading them into the thumbnail field.
Sure, open up issues for these on the lemmy-ui repo.
The resizing an image is out of scope tho, we aren’t going to embed an image suite into lemmy-ui, so you’ll have to do that locally.
Would it be possible to automatically encode the images client side when uploading?
seconded!
-
