[selectors-4][editorial] Make non-normative references more clearly marked so the normative references checker doesn't trip over them so much

svgeesus · svgeesus · commit c282dbebe511 · 2026-07-30T15:47:09.000+03:00
diff --git a/selectors-4/Overview.bs b/selectors-4/Overview.bs
@@ -1359,7 +1359,7 @@ Declaring Namespace Prefixes</h3>
 	should be specified by the language that uses Selectors.
 	If the language does not specify a namespace prefix declaration mechanism,
 	then no prefixes are declared.
-	In CSS, namespace prefixes are declared with the ''@namespace'' rule. [[!CSS3NAMESPACE]]
+	In CSS, namespace prefixes are declared with the ''@namespace'' rule. [[CSS3NAMESPACE]]
 
 <h3 id="invalid">
 Invalid Selectors and Error Handling</h3>
@@ -2055,7 +2055,7 @@ Attribute presence and value selectors</h3>
 			please see the '':lang()'' pseudo-class.
 	</dl>
 
-	Attribute values must be <<ident-token>>s or <<string-token>>s. [[!CSS3SYN]]
+	Attribute values must be <<ident-token>>s or <<string-token>>s. [[CSS3SYN]]
 
 	<div class="example">
 		Examples:
@@ -4024,7 +4024,7 @@ Child-indexed Pseudo-classes</h3>
 	with that of its selector argument <var>S</var>.
 	See [[#specificity-rules]].
 
-	The CSS Syntax Module [[!CSS3SYN]] defines the <a href="https://drafts.csswg.org/css-syntax/#anb"><var>An+B</var> notation</a>.
+	The CSS Syntax Module [[CSS3SYN]] defines the <a href="https://drafts.csswg.org/css-syntax/#anb"><var>An+B</var> notation</a>.
 
 	<div class="example">
 		Examples:
@@ -5099,6 +5099,7 @@ Appendix B: Obsolete but Required <code>-webkit-</code> Parsing Quirks for Web C
 <h2 id="visited-privacy" class="non-normative">
 Appendix C: Example Privacy-Preserving '':visited'' Restrictions</h2>
 
+<p class="non-normative">
 Previous attempts to protect user privacy in '':visited''
 involved <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector">complex restrictions and behaviors</a>
 to "lie" about whether the link match '':visited'' or '':link'',
@@ -5109,7 +5110,10 @@ and help the user know what links they'd already clicked.
 This is ultimately an arms race that can't be won;
 there are multiple documented ways to still extract a user's browsing history
 even with these mitigations.
+</p>
 
+
+<p class="non-normative">
 This section describes an approach first developed and documented at
 <a href="https://github.com/explainers-by-googlers/Partitioning-visited-links-history">https://github.com/explainers-by-googlers/Partitioning-visited-links-history</a>,
 that partitions a user's browsing history information,
@@ -5119,6 +5123,7 @@ With this, '':visited'' can be treated as a normal pseudo-class,
 without any of the complex mitigations described above,
 as it doesn't expose any information not already theoretically available to the site,
 while still preserving as much of the <em>usefulness</em> of '':visited'' as possible for the user.
+</p>
 
 1. Let |visited history| be a [=/set=]
 	containing [=tuples=] of three pieces of information:
@@ -5197,6 +5202,7 @@ while still preserving as much of the <em>usefulness</em> of '':visited'' as pos
 </div>
 
 
+<div class="non-normative">
 <h2 id="changes">
 Changes</h2>
 
@@ -5438,7 +5444,9 @@ Changes since the 29 September 2011 Working Draft</h3>
 		<li>Changed <a>column combinator</a> from double slash to double pipe.
 	</ul>
 
+</div>
 
+<div class="non-normative">
 <h3 id="changes-level-3">
 Changes Since Level 3</h3>
 
@@ -5628,7 +5636,7 @@ Changes Since Level 3</h3>
 		<li>Added '':user-invalid''.
 		<li>Added case-insensitive / case-sensitive attribute-value matching flags.
 	</ul> -->
-
+</div>
 
 <h2 id="acknowledgements">
 Acknowledgements</h2>
