Re: [csswg-drafts] [css-counter-styles] Clarify how @counter-style name lookup works with shadow DOM (#5693)

The CSS Working Group just discussed `[css-counter-styles] Clarify how @counter-style name lookup works with shadow DOM`, and agreed to the following:

* `RESOLVED: Accept the PR linked in the issue defining how counter style scoping works with shadow dom`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-counter-styles] Clarify how @counter-style name lookup works with shadow DOM<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5693<br>
&lt;dael> TabAtkins: We talked previous week about the small change to name defining constructs to work with scoping. This is a request for approval to edit counter styles so that it works with the scoping machinery. Define counter style in outer page you can reference it within shadow dom. If you define it within the same name it stays in the shadow and overrides<br>
&lt;dael> TabAtkins: If you define it in the outer, inherit into a shadow, and redefine you get what you think you should use. Nothing novel, but spec needed a change to hook into that and I wanted approval b/c it is normative<br>
&lt;dael> astearns: Prop: Accept the PR linked in the issue defining how counter style scoping works with shadow dom<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: Accept the PR linked in the issue defining how counter style scoping works with shadow dom<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 2 June 2021 23:54:15 UTC