Fix WPT CSS Counters style containment tests #41820
Merged
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.
As per:
https://drafts.csswg.org/css-contain/#example-6932a400
and
w3c/csswg-drafts#9116
counter() and counters() can cross the style containment boundary
and the first counter-increment will create a counter, that will be
inherited by its siblings, so class="contain" element will have a
counter from its previous sibling, and counters() inside
the style containment scopes will have access to this counter.
Bug: 990657
Reviewed-on: https://chromium-review.googlesource.com/4839207
WPT-Export-Revision: 4ead277cddb50a1adb53cb4b5d76046d1d7bcde9