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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compute responsive
sizes
attribute based on thewidth
from theboundingClientRect
in captured URL Metrics #1840Compute responsive
sizes
attribute based on thewidth
from theboundingClientRect
in captured URL Metrics #1840Changes from 12 commits
4d39880
7b620c2
f964684
f606dac
a9fba2c
74c2ce6
df0c9e2
cdda7c3
6045b18
93961fa
eca53e6
d2b9a5c
4d0251a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this text isn't new, but might be worth clarifying why that's important. Based on how it's currently phrased here, people might argue "But WordPress Core already does this!".
So maybe this can be rephrased to clarify that it's about ensuring that
sizes=auto
is applied correctly after Image Prioritizer has improved/fixed lazy-loading of images as done by WordPress.Since the
sizes=auto
part isn't really a feature this plugin does better than WordPress (it's the lazy-loading portion it does better than WordPress, but not how it appliessizes=auto
), I would put the point of computing the correctsizes
above this, as it's a more powerful feature of the plugin.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like so?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, plus moving it to
#2
in the list as mentioned :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes! Done: 4d0251a
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the
intersectionRect
now automatically is populated to be zeroed out when theinterectionRatio
is 0. Previously it was not making sense to have aDOMRect
containing non-zero values when theintersectionRatio
was zero.Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.