The system, fallback, and decimal descriptors all use <counter-style-name> in their value grammar definition, linking to:
https://drafts.csswg.org/css-counter-styles/#typedef-counter-style-name
The general form of an @counter-style rule is:
@counter-style <counter-style-name> { <declaration-list> }
where <counter-style-name> is a <custom-ident>.
If a counter style’s name is an ASCII case-insensitive match for "decimal" or "none", the @counter-style rule is invalid.
It is unclear whether the exclusion of "decimal" and "none" is part of the definition of the <counter-style-name> type, and therefore also applies when this type is used in descriptors, or whether that only applies to @counter-style rules.
Being able to use "decimal" makes sense. In fact that’s even the initial value, in the case of fallback. Using none less so. Maybe a different behavior is desirable for these two keywords?
By the way, why is "none" excluded when for example "inside" isn’t?
The
system,fallback, anddecimaldescriptors all use<counter-style-name>in their value grammar definition, linking to:https://drafts.csswg.org/css-counter-styles/#typedef-counter-style-name
It is unclear whether the exclusion of "decimal" and "none" is part of the definition of the
<counter-style-name>type, and therefore also applies when this type is used in descriptors, or whether that only applies to@counter-stylerules.Being able to use "decimal" makes sense. In fact that’s even the initial value, in the case of
fallback. Usingnoneless so. Maybe a different behavior is desirable for these two keywords?By the way, why is "none" excluded when for example "inside" isn’t?