[css-cascade-6] link proximity strength issue, and document WG leaning

Author: mirisuzanne

css-cascade-6/Overview.bs

@@ -184,7 +184,7 @@ Cascade Sorting Order</h3>
 			</ul>
 	</dl>
 
-	Issue: Does <dfn>scope proximity</dfn> belong above or below specificity in the cascade?
+	Issue(6790): Does <dfn>scope proximity</dfn> belong above or below specificity in the cascade?
 
 	The <dfn export>output of the cascade</dfn>
 	is a (potentially empty) sorted list of <a>declared values</a> for each property on each element.
@@ -323,21 +323,23 @@ Scoped Styles</h2>
 -->
 
 <h4 id='scope-atrule'>
-Strong Scoping: the ''@scope'' rule</h4>
+Scoping Styles: the ''@scope'' rule</h4>
 
 	The <dfn>@scope</dfn> [=block at-rule=]
 	allows authors to scope style rules in CSS,
-	with the application of [=scoping proximity=]
+	with the application of [=weak scoping proximity=]
 	between the [=scoping root=] and the [=subject=] of each style rule.
 	<!-- This causes declarations [insert appropriate sentence from issue below]. -->
 
-	ISSUE: Should ''@scope'' use strong or weak scoping proximity?
+	Issue(6790): Should ''@scope'' use strong or weak scoping proximity?
 	[=Strong scoping proximity=] causes declarations to be weighted more strongly
 	by scope proximity than by their selector’s specificity.
 	[=Weak scoping proximity=] causes declarations of the same specificity
 	to be weighted by proximity to their scoping root
 	before falling back to source ordering,
 	but declarations of higher specificity win over more tightly-scoped declarations.
+	The Working Group currently leans towards weak proximity,
+	and recommends that as a starting point for prototypes.
 
 	The syntax of the ''@scope'' rule is:
 
@@ -466,10 +468,14 @@ Scoped Descendant Combinator</h4>
 
 	This combinator differs from the [=descendant combinator=]
 	in that it applies [=weak scoping proximity=]
-	to the relationship between ''A'' and <css>B</css>.
+	to the relationship between <css>A</css> and <css>B</css>.
 	It does not change the [=:scope element=].
 
-	ISSUE: Should the [=scoped descendant combinator=] use strong or weak scoping proximity? Should it even exist? It's defined here to work the way many people expected the regular [=descendant combinator=] to work...
+	ISSUE: Should the [=scoped descendant combinator=]
+	use strong or weak scoping proximity?
+	Should it even exist?
+	It's defined here to work the way many people expected
+	the regular [=descendant combinator=] to work...
 
 	<div class="example">
 		This means that style rules using the [=scoped descendant combinator=]