[resize-observer-1] ResizeObserverEntry properties future proofing for fragment support #3673 #4529
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
dlibby-
force-pushed
the
resize-observer-fragment-support
branch
from
40b4548 to
eb9a2c7
Compare
chrishtr
approved these changes
Nov 22, 2019
# for free
to join this conversation on GitHub.
Already have an account?
# to 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.
Minutes: #3673 (comment)
The working group resolution was to have the ResizeObserverEntry box size properties return sequences instead of a single value, to better support fragments. This change modifies the idl accordingly and adds some explanation of why this is, and updates algorithms/references to the properties to be aware of the sequence