W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2017

Re: [csswg-drafts] [css-counter-styles] Invalid @counter-style should just not define a counter style, not be ignored

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Oct 2017 16:32:07 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-335868951-1507739512-sysbot+gh@w3.org>
The Working Group just discussed `Invalid @counter-style should just not define a counter style, not be ignored`, and agreed to the following resolutions:

* `RESOLVED: treat invalid counter styles the way we treat invalid font faces`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Invalid @counter-style should just not define a counter style, not be ignored<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1682<br>
&lt;dael> TabAtkins: The problem is what precisely do we do with counterstyle rules that are invalid due to either not having or missing required properties. Is it invalid or does it not define one?<br>
&lt;dael> TabAtkins: Fontface has some required descriptors and if you're missing them it just fails to instantiate a font face. I propose to mirror font face so they stay in the OM.<br>
&lt;dael> florian: Compat req?<br>
&lt;dael> TabAtkins: No. FF is only impl and xidorn is okay either way.<br>
&lt;dael> dbaron: sgtm<br>
&lt;dael> astearns: Obj to treat invalid counter styles the way we treat invalid font faces?<br>
&lt;dael> RESOLVED: treat invalid counter styles the way we treat invalid font faces<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1682#issuecomment-335868951 using your GitHub account
Received on Wednesday, 11 October 2017 16:31:55 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:19 UTC