diff --git a/css-cascade-6/Overview.bs b/css-cascade-6/Overview.bs index 3792ea36116f..4ab0a1d80634 100644 --- a/css-cascade-6/Overview.bs +++ b/css-cascade-6/Overview.bs @@ -526,75 +526,6 @@ Scoped Descendant Combinator - Note: Most simple scoping relationships can be represented with this syntax, - rather than the more complex [=selector scoping notation=] defined below. - -

-Selector Scoping Notation

- - The selector scoping notation - allows [=selectors=] to be scoped - to a subtree of the document, - and allows the possibility of excluding nested subtrees. - It is prepended to the selector or selector list, - and its syntax is as follows: - - 
-	<> = ( <> [/ <>]? )
-
- - If, after parsing, <> is an empty list, - the selector is valid but matches nothing. - Otherwise, the selector matches any element - that is within the [=scope=] described - by the given <> and <> selectors. - -
- The purpose of the [=selector scoping notation=] - is to allow adding [=scoping limits=] to a selector: - - 
-		(.post / .comments) .title { font-size: 2em; }
-
- - Without any such lower limits, - the [=selector scoping notation=] is similar to existing descendant selectors, - except that the [=scoping root=] can be matched - by the selector as well. -
- - The specificity of - the most specific [=complex selector=] in <> - is added to the specificity of each such scoped selector. - The specificity of the <> is ignored. - The [=selector scoping notation=] also applies [=weak scoping proximity=] - between the [=scoping root=] and the [=subject=] of the scoped selector. - - ISSUE: Should this have the same [=scope proximity=] weighting as ''@scope'' - or different [=scope proximity=] weighting - (or no [=scope proximity=] weighting)? - -
- For example, - these three selectors will all select the same elements, - with the same specificity: - - 
-		(.ancestor) .child                { color: darkmagenta; }
-		.child:is(.ancestor, .ancestor *) { color: darkmagenta; }
-		.ancestor.child, .ancestor .child { color: darkmagenta; }
-
- - However the first rule will win, - because it also applies [=weak scoping proximity=]. -
- - ISSUE: How does this interact with [[CSS-NESTING-1]]? - - ISSUE: This notation was added in order to allow scoping limits - to be applied within querySelector(). - Is this something we want to have? -

Precedence of Non-CSS Presentational Hints

@@ -622,6 +553,9 @@ Changes since the 21 December 2021 First Public Working Draft Significant changes since the 21 December 2021 First Public Working Draft include: + * Removed selector scoping notation. + (Issue 7709) + * [=Scoping limit=] elements are excluded from the resulting [=scope=]. (Issue 6577)