- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Aug 2024 10:33:22 +0000
- To: public-css-archive@w3.org
OK reading https://drafts.csswg.org/css-counter-styles/#the-counter-style-rule: """ This at-rule conforms with the forward-compatible parsing requirement of CSS; conformant parsers that don’t understand these rules will ignore them without error. Any descriptors that are not recognized or implemented by a given user agent, or whose value does not match the grammars given here or in a future version of this specification, must be ignored in their entirety; they do not make the [@counter-style](https://drafts.csswg.org/css-counter-styles/#at-ruledef-counter-style) rule invalid. """ I think that this should be the case for this rule as well, and we should change `navigaiton` to be a `CSSOMString` (like https://drafts.csswg.org/css-counter-styles/#the-csscounterstylerule-interface) that returns an empty string when there is no valid navigation rule, as per the current chromium implementation. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10654#issuecomment-2296248515 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 August 2024 10:33:23 UTC