[Gecko Bug 1808995] Fix WPT testcases that do not properly account for counter-style fallback behavior of prefix/suffix descriptors. #38219
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.
Per spec, "If a counter style is used to represent a counter value outside of its ranges,
the counter style instead drops down to its fallback counter style."
https://www.w3.org/TR/css-counter-styles-3/#counter-style-range
https://www.w3.org/TR/css-counter-styles-3/#counter-style-fallback
Some existing tests incorrectly assumed that a prefix or suffix from a custom rule will still apply
even when the counter value is not in range. That would mean "fallback" is only partial, using
the symbols/system from the fallback style mixed with the prefix/suffix of the originally-specified
style, which prevents use-cases like that in bug 1808995 working as expected.
Differential Revision: https://phabricator.services.mozilla.com/D167410
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1808995
gecko-commit: c2a49ee389d95fef709a326f089033aa362543aa
gecko-reviewers: emilio