Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Gecko Bug 1808995] Fix WPT testcases that do not properly account for counter-style fallback behavior of prefix/suffix descriptors. #38219

Merged
merged 3 commits into from Jan 29, 2023

Conversation

moz-wptsync-bot
Copy link
Collaborator

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

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Firefox project.

…back behavior of prefix/suffix descriptors.

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: ed181fad393482cfd7961b1aa9d322da8009b485
gecko-reviewers: emilio
…tom style's range.

Differential Revision: https://phabricator.services.mozilla.com/D167411

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1808995
gecko-commit: f43c5a2967b47dd473b7f55430dc4937ef735770
gecko-reviewers: emilio
…k chain.

Differential Revision: https://phabricator.services.mozilla.com/D168051

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1808995
gecko-commit: 809ead0307798a50c8e9a8fb968b6100f4200d66
gecko-reviewers: emilio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants