- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Sep 2023 18:55:02 +0000
- To: public-css-archive@w3.org
> To me that essentially means we take all the elements inside the subtree excluding the scoping element, and put that in its own document. Meaning the counter should always be "0" where we read the counter, since the counter is never incremented (since the element that increments it is outside of that "document"). From an authoring perspective, this mental model makes sense to me... But I think this gets to the fundamental question of, what is style containment? Does it only prevent content within the contained subtree from affecting content outside it, or does it also prevent styling from outside the subtree from affecting content inside it? For example, what happens with timeline names? If an ancestor of the contained element declares a named timeline, can content inside the subtree reference it? Counters should be consistent with that. What are the use cases for style containment, and which mental model are we targetting here? -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9212#issuecomment-1736104295 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 September 2023 18:55:04 UTC