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
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
We're getting questions about why ResizeController causes two consecutive host updates. It seems like ResizeObservers already call the observer callback unconditionally, so our code to do that as well made there be two updates. Can we just remove our custom initial call to handleChanges? This would let us remove skipInitial altogether.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Yeah, I think this stemmed from the fact that the other observers don't have an initial report.
Couple observations. These tests appear to be wrong here since the skipInitial test should be failing. I think it's because we're not waiting until ResizeObserver triggers (fix: maybe just change the await here to be resizeComplete:
I'd like to preserve the skipInitial setting since we have that on the other observers. To do so we could just do something like in the main observer callback (
After fixing the tests and applying the skipInitial setting in the same way that IntersectionController does it, we end up with all tests passing except Safari. This is due to WebKit not calling the callback on observe at the moment. They are working on changing the behavior to match Chrome and Firefox. See: webcompat/web-bugs#117611 (comment)
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.
We're getting questions about why ResizeController causes two consecutive host updates. It seems like ResizeObservers already call the observer callback unconditionally, so our code to do that as well made there be two updates. Can we just remove our custom initial call to handleChanges? This would let us remove skipInitial altogether.
wdyt @sorvell ?