fix typo and improve articulation #42038
Open
+1
−1
Conversation
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
prakhar-pal
requested review from
chrisdavidmills
and removed request for
a team
github-actions
bot
added
Content:HTML
prakhar-pal
changed the title
Contributor
|
Preview URLs Flaws (20)URL:
|
chrisdavidmills
requested changes
Nov 21, 2025
Contributor
chrisdavidmills
left a comment
chrisdavidmills
left a comment
There was a problem hiding this comment.
Thanks for improving this, @prakhar-pal. What you've done so far is good, but I have a further suggestion for you to consider.
| - : Defers loading the image until it reaches a calculated distance from the viewport, as defined by the browser. The intent is to avoid the network and storage bandwidth needed to handle the image until it's reasonably certain that it will be needed. This generally improves the performance of the content in most typical use cases. | ||
|
|
||
| While explicit [`width`](#width) and [`height`](#height) attributes are recommended for all images to avoid layout shift, they are especially important for lazy-loaded ones. Lazy-loaded images will never be loaded if they do not intersect a visible part of an element, even if loading them would change that, because unloaded images have a `width` and `height` of `0`. It is also more a more disturbing user experience if the page reflows in the middle of reading. | ||
| While explicit [`width`](#width) and [`height`](#height) attributes are recommended for all images to avoid layout shift, they are especially important for lazy-loaded ones. Lazy-loaded images will never be loaded if they do not intersect a visible part of an element, even if loading them would change that, because unloaded images have a `width` and `height` of `0`. It also creates a more disruptive user experience when the page reflows in the middle of reading. |
Contributor
There was a problem hiding this comment.
Suggested change
| While explicit [`width`](#width) and [`height`](#height) attributes are recommended for all images to avoid layout shift, they are especially important for lazy-loaded ones. Lazy-loaded images will never be loaded if they do not intersect a visible part of an element, even if loading them would change that, because unloaded images have a `width` and `height` of `0`. It also creates a more disruptive user experience when the page reflows in the middle of reading. | |
| While explicit [`width`](#width) and [`height`](#height) attributes are recommended for all images to avoid layout shift, they are especially important for lazy-loaded ones. Lazy-loaded images will never be loaded if they do not intersect a visible part of an element, even if loading them would change that, because unloaded images have a `width` and `height` of `0`. It creates an even more disruptive user experience when the content visible in the viewport reflows in the middle of reading it. |
Contributor
There was a problem hiding this comment.
What you've done so far is good, but I wonder if the sentence should be modified further to something like this. The page already mentions setting width/height to avoid layout shift, and that this is important, in a note inside the height description. So the existing text here seems a bit repetitive. I think it is supposed to say that the layout shift is particularly bad when you don't set width/height on lazy-loaded images because the shift can happen to the currently-visible content.
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
This PR fixes a typo in the img documentation (the changed sentence contained duplicate
more). I've also improved articulation of that sentence to read more naturallyMotivation
Mainly to fix the typo and additionally to improve concept's articulation.
Additional details
Related issues and pull requests