- From: Simon Sapin via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Apr 2017 07:51:31 +0000
- To: public-css-archive@w3.org
SimonSapin has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-counter-styles] `system: extends decimal; fallback: decimal; speak-as: decimal` ==
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:
>
> ```css
> @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?
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1285 using your GitHub account
Received on Monday, 24 April 2017 07:51:38 UTC