[scroll-animations] Clarify proximity with nested @scope rules

w3c#8380
andruud · Apr 14, 2023 · e0150e6 · e0150e6
1 parent 081014b
commit e0150e6
Showing 1 changed file with 3 additions and 5 deletions.
diff --git a/css-cascade-6/Overview.bs b/css-cascade-6/Overview.bs
@@ -154,11 +154,6 @@ Cascade Sorting Order</h3>
 			then the declaration with the fewest generational hops
 			between the ancestor/descendant element pair wins.
 
-			If multiple such pairs are represented,
-			their [=scoping proximity=] weights are compared
-			from innermost scoping relationship to outermost scoping relationship
-			(with any missing pairs weighted as infinity).
-
 		<dt id='cascade-order'>Order of Appearance
 		<dd>
 			The last declaration in document order wins.
@@ -321,6 +316,9 @@ Effects of ''@scope''</h4>
 	selectors within an ''@scope'' rule
 	do not acquire the specificity of any parent selector(s) in the ''@scope'' prelude.
 
+	Note: For [[#scope-scope|nested @scope rules]],
+	only the innermost ''@scope'' matters for determining [=scoping proximity=].
+
 	<div class=example>
 		The following selectors have the same specificity (0,0,1):