Intent to ship: CSS reversed() counters

[Mats Palmgren]

Summary: This implements reversed counters in CSS and maps
HTML <ol reversed> to use that internally.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1706346
Standard: https://drafts.csswg.org/css-lists/#typedef-reversed-counter-name
plus resolutions in https://github.com/w3c/csswg-drafts/issues/6738 and
https://github.com/w3c/csswg-drafts/issues/6797
Platform coverage: All
Preference: none
Other browsers: no support yet AFAIK
web-platform-tests: yes, some existing + added a lot more

[Anne van Kesteren]

On Sun, Nov 14, 2021 at 5:09 AM Mats Palmgren <ma...@mozilla.com> wrote:
> Summary: This implements reversed counters in CSS and maps
> HTML <ol reversed> to use that internally.

Does it end up matching the end of this section:
https://html.spec.whatwg.org/multipage/rendering.html#lists? Given the
recent changes on the CSS side you pointed out, I wonder how accurate
that is.

[Mats Palmgren]

It looks correct to me, i.e. it's unaffected by these changes
in CSS Lists. These changes doesn't affect markup that has an
explicit 'start' attribute. The section you refer to says
"Otherwise, return 'reversed(list-item)'" which (correctly)
leaves calculating a start value to CSS Lists.
(It's that calculation which has changed slightly in some
edge cases with the latest resolutions.)


/Mats

[Anne van Kesteren]

On Wed, Nov 17, 2021 at 12:32 PM Mats Palmgren <ma...@mozilla.com> wrote:
> It looks correct to me, i.e. it's unaffected by these changes
> in CSS Lists. These changes doesn't affect markup that has an
> explicit 'start' attribute. The section you refer to says
> "Otherwise, return 'reversed(list-item)'" which (correctly)
> leaves calculating a start value to CSS Lists.
> (It's that calculation which has changed slightly in some
> edge cases with the latest resolutions.)

That's great, thanks for checking!