Skip to content

Commit 14969b2

Browse files
authored
[scroll-animations] Clarify proximity with nested @scope rules (w3c#8722)
w3c#8380
1 parent 081014b commit 14969b2

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

css-cascade-6/Overview.bs

+3-5
Original file line numberDiff line numberDiff line change
@@ -154,11 +154,6 @@ Cascade Sorting Order</h3>
154154
then the declaration with the fewest generational hops
155155
between the ancestor/descendant element pair wins.
156156

157-
If multiple such pairs are represented,
158-
their [=scoping proximity=] weights are compared
159-
from innermost scoping relationship to outermost scoping relationship
160-
(with any missing pairs weighted as infinity).
161-
162157
<dt id='cascade-order'>Order of Appearance
163158
<dd>
164159
The last declaration in document order wins.
@@ -321,6 +316,9 @@ Effects of ''@scope''</h4>
321316
selectors within an ''@scope'' rule
322317
do not acquire the specificity of any parent selector(s) in the ''@scope'' prelude.
323318

319+
Note: For [[#scope-scope|nested @scope rules]],
320+
only the innermost ''@scope'' matters for determining [=scoping proximity=].
321+
324322
<div class=example>
325323
The following selectors have the same specificity (0,0,1):
326324

0 commit comments

Comments
 (0)