[css-nesting-1] Drop the issue about doing something complicated for serializing nested rules, and instead put notes in calling out the serialization differences.

Author: tabatkins

css-nesting-1/Overview.bs

@@ -721,6 +721,11 @@ Nesting Other At-Rules {#conditionals}
 	and nested in a [=nested style rule=]
 	with the selector ''&'',
 	and placed before all other child rules.
+	This includes in the OM.
+	(That is,
+	the {{CSSContainerRule/childRules}} attribute
+	actually starts with this [=nested style rule=],
+	containing all the directly-nested properties.)
 
 	<div class=example>
 
@@ -755,10 +760,10 @@ Nesting Other At-Rules {#conditionals}
 		containing the 'grid-auto-flow' property.
 	</div>
 
-	Issue: Need to modify the serialization rules,
-	as in <a href="https://github.com/w3c/csswg-drafts/issues/7850#issuecomment-1288883780">this comment</a>,
-	to remove the wrapping rule
-	when the first child rule is <code>& {...}</code>.
+	Note: This does mean that the serialization of such rules will differ
+	from how they were originally written,
+	with <em>no</em> directly-nested properties in the serialization.
+
 
 <h4 id=nesting-at-scope>
 Nested ''@scope'' Rules</h4>
@@ -883,6 +888,13 @@ Mixing Nesting Rules and Declarations {#mixing}
 	due to specifics of how parsing and error-recovery work,
 	properties appearing after nested rules can get skipped.)
 
+	Note: Like with other types of rules,
+	the serialization of style rules in the presence of nesting
+	can vary from how they were originally written.
+	Notably, all directly-nested properties
+	will be serialized before any nested rules,
+	which is <em>another</em> reason to write properties before rules.
+
 
 <!--
   ████