Re: [csswg-drafts] [css-contain] Do scoped counters create new counters?

The Working Group just discussed `Scoped Counters`, and agreed to the following resolutions:

* `RESOLVED: create new counter scopes at style scoping root for style containment`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Scoped Counters<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/1887<br>
&lt;fantasai> TabAtkins: If you have a style scoped element, which says counters are scoped to the subtree<br>
&lt;fantasai> TabAtkins: does that create a new counter?<br>
&lt;fantasai> s/that/counter-increment/<br>
&lt;fremy> +1 on this one<br>
&lt;fantasai> TabAtkins: or does it increment the existing counter from the outside<br>
&lt;fantasai> TabAtkins: I think it should implicitly create a new counter scope at the style scoping root<br>
&lt;fantasai> fantasai: And so counters() would reveal a new level of counter?<br>
&lt;fantasai> TabAtkins: yes<br>
&lt;fantasai> TabAtkins: Don't want to fuss with the subtree when calculating counters further down in the document<br>
&lt;fantasai> fantasai: so you're disagreeing with Oriol's comment?<br>
&lt;fantasai> TabAtkins: ...<br>
&lt;fantasai> astearns: Write a test?<br>
&lt;TabAtkins> s/.../yes/<br>
&lt;fantasai> astearns: So proposed to implicitly create new counter scopes at style scoping root for style containment<br>
&lt;fantasai> RESOLVED: create new counter scopes at style scoping root for style containment<br>
</details>


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

Received on Tuesday, 7 November 2017 00:33:50 UTC