Re: [csswg-drafts] [css-lists][css-counter-styles] Compute list-style-type to 'decimal' if the specified counter style does not exist

The CSS Working Group just discussed `CSS Counter style issues.`, and agreed to the following resolutions:

* `RESOLVED: No change.`
* `RESOLVED: No change to CR; revert the change to the Editor's draft.`

<details><summary>The full IRC log of that discussion</summary>
&lt;iank_> Topic: CSS Counter style issues.<br>
&lt;astearns> https://drafts.csswg.org/css-counter-styles-3/issues-cr-20150611<br>
&lt;glazou> argl<br>
&lt;fantasai> https://drafts.csswg.org/css-counter-styles-3/issues-cr-20150611#issue-7<br>
&lt;fantasai> https://lists.w3.org/Archives/Public/www-style/2016May/0076.html<br>
&lt;iank_> fantasai: This is about a counter style which hasn't been created, its kept around and defaulted to decimal<br>
&lt;fantasai> s/about a/about using a/<br>
&lt;iank_> astearns: Seems fine.<br>
&lt;fantasai> fantasai^: Proposal was to compute it to decimal, not keeping around the name<br>
&lt;iank_> fremy: Why would you want to do that in the first place,<br>
&lt;iank_> Rossen: Simplifies code, xidorn also said this wasn't a big issue.<br>
&lt;iank_> fremy: It would for use require a lot of code.<br>
&lt;iank_> fremy: Need some code which would replace the computed style.<br>
&lt;iank_> fantasai: Computed style isn't just used in the om<br>
&lt;iank_> fantasai: I'm not sure why it would be harder to switch unknown values to decimal.<br>
&lt;fantasai> s/om/om, also has to inherit/<br>
&lt;iank_> fremy: In edge you don't need a computed value, if you have a specified value.<br>
&lt;fantasai> s/need/need to store/<br>
&lt;iank_> fremy: When the style is being defined you need to it is going to change the computed style a bunch, you need to invalidate all the styles on the page.<br>
&lt;iank_> Rossen: Going back to the issue,<br>
&lt;fantasai> Basically what François is saying is that if you use an undefined counter style, and the UA computes it to decimal, and then we append an @counter-style rule defining the counter style, this invalidates the computed styles<br>
&lt;iank_> Rossen: xidorn didn't sound too insistent on it, TabAtkins said whatever, which ever way is more consistent.<br>
&lt;iank_> Rossen: At least 1 impl, which will require more cycles to support this, can we live without the simplification?<br>
&lt;iank_> Rossen: I'm mostly interested in moz folks.<br>
&lt;iank_> fantasai: you need to hear from mozilla, and anyone else who is going to impl this.<br>
&lt;iank_> Bert: Is it possible for an unresolved name to define later in the tree.<br>
&lt;iank_> fantasai: No its global scope,<br>
&lt;iank_> Rossen: Since fantasai is looking for resolution, can we resolve to not simplify? Anyone objecting?<br>
&lt;iank_> dbaron: Would be good to hear for xidorn ....<br>
&lt;iank_> Rossen: He didn't think it would be a big deal....<br>
&lt;iank_> RESOLVED: No change.<br>
&lt;fantasai> ACTION TabAtkins revert change in ED<br>
&lt;trackbot> Created ACTION-853 - Revert change in ed [on Tab Atkins Jr. - due 2017-08-09].<br>
&lt;dbaron> RESOLVED: No change to CR; revert the change to the Editor's draft.<br>
&lt;dbaron> github: https://github.com/w3c/csswg-drafts/issues/1616<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1616#issuecomment-319600580 using your GitHub account

Received on Wednesday, 2 August 2017 08:09:46 UTC