- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Jan 2019 21:56:23 +0000
- To: public-css-archive@w3.org
Response by @tabatkins 2015-01-20 > Unfortunately, this problem is unavoidable with current properties. > Previously, when the set of counter-styles was defined by the language, we could tell at parse time whether the value was valid or not, and reject the declaration if it was invalid. That gave you the older behavior, of still using bullets or numbers, as it could fall back to the UA stylesheet. > With the introduction of @counter-style, though, we can't do that any longer. The set of valid counter style names isn't known at parse-time, as it depends on other rules in the stylesheet (or in other stylesheets, perhaps from different domains). Thus, we can't reject an unknown value at parse time and fall back any longer. > If we can't fall back, then there needs to be *some* defined behavior for what to do when, at run-time, we find out the counter-style name is invalid. For lack of a better option, and for consistency with a few other bits, I chose to default it to "decimal". We can't change fallback for "ordered" or "unordered" lists, because that information doesn't exist for CSS. At best, we have tagnames, which is a hacky HTML-specific solution that doesn't work well. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3563#issuecomment-458317524 using your GitHub account
Received on Monday, 28 January 2019 21:56:25 UTC