From e48aaf619080f7b89d689317d8d585b11c425ca9 Mon Sep 17 00:00:00 2001 From: andruud Date: Tue, 21 Oct 2025 09:42:10 +0200 Subject: [PATCH] [css-nesting-1] Fix character reference errors For example: LINE 330:39: Character reference '&Bar' didn't end in ;. Replaced various instances of '&' with '&'. --- css-nesting-1/Overview.bs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/css-nesting-1/Overview.bs b/css-nesting-1/Overview.bs index f129509aba7..a8d83a737b5 100644 --- a/css-nesting-1/Overview.bs +++ b/css-nesting-1/Overview.bs @@ -327,10 +327,10 @@ Syntax {#syntax} as nesting is not a syntax transformation, but rather matches on the actual elements the parent selector matches. - It is also true that the selector ''&Bar'' is invalid in CSS in the first place, + It is also true that the selector ''&Bar'' is invalid in CSS in the first place, as the ''Bar'' part is a type selector, which must come first in the compound selector. - (That is, it must be written as ''Bar&''.) + (That is, it must be written as ''Bar&''.) So, luckily, there is no overlap between CSS Nesting and the preprocessor syntax. @@ -1091,10 +1091,10 @@ Nesting Selector: the ''&'' selector {#nest-selector} While the position of a [=nesting selector=] in a [=compound selector=] does not make a difference in its behavior - (that is, ''&.foo'' and ''.foo&'' match the same elements), + (that is, ''&.foo'' and ''.foo&'' match the same elements), the existing rule that a [=type selector=], if present, must be first in the [=compound selector=] continues to apply - (that is, ''&div'' is illegal, and must be written ''div&'' instead). + (that is, ''&div'' is illegal, and must be written ''div&'' instead).