Repository navigation
Conversation
…ip it Chrome 155 (2026-10-06) and Firefox 158 (2026-10-13) enabled JPEG XL, joining Safari 17+. Edge has not, so webstatus.dev still reports it as limited availability. The page now recommends it as an extra <picture> source rather than a replacement for AVIF, and notes the Vary: Accept requirement for servers that negotiate on Accept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
6fdc142
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c6c7e733.specification-website.pages.dev |
| Branch Preview URL: | https://scan-2026-10-19-jpeg-xl.specification-website.pages.dev |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The
performance/image-optimizationpage now has a paragraph on JPEG XL, andupdatedis bumped to 2026-10-19.jpegxlreportslimited.<picture>source, not a replacement for AVIF. It names the wrong belief readers arrive with: shipping in three engines is not the same as Baseline, and JPEG XL is not simply a smaller AVIF.image/jxlin its imageAcceptheader. The page notes that Accept-negotiating servers needVary: Accept, linking/spec/performance/vary/.Why now
Firefox 158 shipped on 13 Oct, the second of the two engines to enable JPEG XL in October. The page said nothing about JPEG XL.
Sources
image/jxlregistered, reference ISO/IEC JTC 1/SC 29/WG 1 (ISO/IEC 18181)Acceptvalue. Cited inline.jpegxl: per-browser versions and dates, Edge missing.The front-matter
sourcesare unchanged (already at four). The new claims are linked inline instead.Status
The status stays
required. The page's requirement is "modern format, right size, explicit dimensions", and JPEG XL is an optional extra within that.Changelog — borderline, your call
I added
src/content/changelog/2026-10-19-jpeg-xl.md(changed). It's a new paragraph of guidance, not a full rewrite. If you'd rather not log it, delete that file. If this merges after the 19th, re-date the entry and rename the file before merging.Checks
npm run buildpasses,format:checkpasses, andcheck:skillpasses (177 pages).@sentry/browser.npm installfixed it, and I reverted thepackage-lock.jsonchurn it caused, so it isn't in this PR.🤖 Generated with Claude Code