- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Apr 2018 02:09:54 +0000
- To: public-css-archive@w3.org
> Anyways, various CSS specs assume that there is a single root element, but if the scoping element is "outside" the tree, I guess its children are "roots". So you are dropping an important CSS invariant like it's nothing. For example, if the parent of these children is "outside" the tree, are they still considered to be siblings? This is important for counter inheritance. I suggest clarifying that when considering the effects of the property of elements inside the subtree, the element at the base of the subtree is the root. Howver, when considering the effects of the property on the element at the base of the subtree itself, then scoping has no effect and the element itself is counted as "outside" the tree, like the rest of the document. > But in bug #1887 it was resolved that new counters should be created "at style scoping root" (I guess this refers to the contained element and not to its children which become "roots" because their parent is "outside" the tree). I agree with you, but since this differs from what chrome does, I'd like to check in with the WG before updating the spec accordingly. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2349#issuecomment-379128721 using your GitHub account
Received on Friday, 6 April 2018 02:09:55 UTC