intersection-observer: don't use premeasure if there is a more recent measure #30188
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.
summary
Fixes an issue with
intersect-resources
experiment where it can use an out-of-date rect. Specifically we were seeing a regression inamp-ad
where a carousel 1.0 slides were not being laid out at all. This is due to a mismatch inisDisplayed
between the premeasure rect and the more-recent measure within owners.The sequence of events that causes this bug were:
isDisplayed
with the premeasuredRect - see below for the snippet that does the skipping.amphtml/src/service/resources-impl.js
Lines 1547 to 1556 in cc14c96
There are numerous ways of trying to fix this. The first two I thought of were:
I went with (2) within this PR
repro html