W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-contain] "scoped to an element" definition is unused (?)

From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
Date: Fri, 29 Jun 2018 10:49:44 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-401319909-1530269383-sysbot+gh@w3.org>
If reordering the definitions makes it harder to explain, I would at least separate them, like

> A scoped can have its effects scoped to a particular element or subtree.
> - If **scoped to an element**, it must act as if the scoping element was the root of the document for the purpose of evaluating the property’s effects: any uses of the property outside the scoping element must have no effect on the uses of the property on or in the scoping element, and vice versa.
> - If **scoped to a sub-tree**, it’s the same, except the scoping element itself is counted as "outside" the tree, like the rest of the document, and the effects of the property on that element are unaffected by scoping. When considering the effects of the scoped property on elements inside the subtree, the element at the base of the subtree is treated as if it was the root of the document.

And then link directly to "scoped to a sub-tree"

> The counter-increment and counter-set properties must be <a href="#">scoped to the element’s sub-tree</a> and create a new counter.

Currently if you click the link you are pointed to "scoped to an element", can be misleading.

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2845#issuecomment-401319909 using your GitHub account
Received on Friday, 29 June 2018 10:49:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 29 June 2018 10:49:50 UTC