[css-contain] Clarify definitions of scoped properties

Closes w3c#2845

Author: frivoal

css-contain-1/Overview.bs

@@ -290,12 +290,12 @@ Style Containment</h3>
 	Giving an element <dfn export>style containment</dfn> has the following effects:
 
 	1. The 'counter-increment' and 'counter-set' properties
-	    must be <a for=property>scoped</a> to the element's sub-tree
+	    must be <a for=property>scoped to the element's sub-tree</a>
 	    and create a new counter.
 
 	2. The effects of the 'content' property's
 	    ''content/open-quote'', ''content/close-quote'', ''content/no-open-quote'' and ''content/no-close-quote''
-	    must be <a for=property>scoped</a> to the element's sub-tree.
+	    must be <a for=property>scoped to the element's sub-tree</a>.
 
 	    Note: This implies that the depth of quote nesting in the subtree
 	    is unchanged and starts at the value that its context normally implies,
@@ -305,17 +305,22 @@ Style Containment</h3>
 	Note: [[CSS-REGIONS-1]] has normative requirements on how <a>style containment</a> affects regions.
 
 	A <dfn export for=property lt="scoped | scoped property | scoped properties">scoped property</dfn> has 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 <em>inside</em> the subtree,
-	the element at the base of the subtree is treated as if it was the root of the document.
+
+	* If <dfn export for=property lt="scoped to an element | scoped to the element">scoped to an element</dfn>,
+	    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.
+
+	    Note: “Scoping to an element” is currently unused.
+	    It is defined as an exention point for future specifications to use.
+
+	* If <dfn export for=property lt="scoped to a sub-tree | scoped to the sub-tree | scoped to the element's sub-tree | scoped to an element's sub-tree">scoped to a sub-tree</dfn>, 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 <em>inside</em> the subtree,
+	    the element at the base of the subtree is treated as if it was the root of the document.
 
 	<div class=example>
 	As 'counter-increment' is scoped to an element's subtree,
@@ -469,6 +474,7 @@ This appendix is <em>informative</em>.
 * Size containment does not apply to tables
 * Clarify that the columns and grid properties affect the size of size-contained elements
 * Change the animation type of the contain property from discrete to not animatable
+* Editorial improvements
 
 <h3 id="2017-08-08-changes">Changes from the
 <a href="https://www.w3.org/TR/2017/CR-css-contain-1-20170808/">Candidate Recommendation of 8 August 2017</a></h3>

css-contain-1/issues-2018-cr.html

@@ -58,6 +58,14 @@ <h1>CSS Contain Level 1 Disposition of Comments for 2018-05-24 CR</h1>
 Response: <a href='https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750'>https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750</a>
 Closed:   Accepted
 Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750'>https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750</a></pre>
+<pre class='a' id='issue-4'>
+Issue 4. <a href='#issue-4'>#</a>
+Summary:  "scoped to an element" definition unused or unclear
+From:     Daniel Holbert
+Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2845'>https://github.com/w3c/csswg-drafts/issues/2845</a>
+Response: <a href='https://github.com/w3c/csswg-drafts/issues/2845#issuecomment-401319909'>https://github.com/w3c/csswg-drafts/issues/2845#issuecomment-401319909</a>
+Closed:   Accepted
+Resolved: Editorial</pre>
 <script>
 (function () {
     var sheet = document.styleSheets[0];

css-contain-1/issues-2018-cr.txt

@@ -28,3 +28,11 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/2737
 Response: https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750
 Closed:   Accepted
 Resolved: https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750
+----
+Issue 4.
+Summary:  "scoped to an element" definition unused or unclear
+From:     Daniel Holbert
+Comment:  https://github.com/w3c/csswg-drafts/issues/2845
+Response: https://github.com/w3c/csswg-drafts/issues/2845#issuecomment-401319909
+Closed:   Accepted
+Resolved: Editorial