Clarify image format selection guidance - #45339
Open
33modeling wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
Content:HTML
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
2 participants
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.
Description
Replaces the format-by-format list on the img element page with concise guidance about choosing formats based on compression, browser support, and image requirements. It also explains fallbacks and the progressive-rendering benefit of JPEG XL for large images.
Motivation
The previous list called several competing formats a good choice without clearly explaining how to decide between them. This revision directs readers to WebP or AVIF for raster compression, SVG for scalable graphics, and picture-based fallbacks where browser support requires them.
Additional details
Related issues and pull requests
Fixes #45286