You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding is LCP is supposed to factor in the intrinsic sizes of images and not consider the rendered size for LCP in cases where the image is stretched or enlarged (e.g. a 1px transparent gif).
It's also not clear from the spec that this is supposed to happen (see: w3c/element-timing#31).
The explainer should be updated to reflect the intention (and I believe the current Chrome implementation).
The text was updated successfully, but these errors were encountered:
npm1
changed the title
Explains incorrectly claims LCP reports the visual size of images
Explainer incorrectly claims LCP reports the visual size of images
Aug 9, 2019
My understanding is LCP is supposed to factor in the intrinsic sizes of images and not consider the rendered size for LCP in cases where the image is stretched or enlarged (e.g. a 1px transparent gif).
The explainer, however, just mentions the visual size:
https://github.com/WICG/largest-contentful-paint#visual-size
It's also not clear from the spec that this is supposed to happen (see: w3c/element-timing#31).
The explainer should be updated to reflect the intention (and I believe the current Chrome implementation).
The text was updated successfully, but these errors were encountered: