[css-overflow-3] Move sections around. No changes.

Author: fantasai

css-overflow-3/Overview.bs

@@ -376,23 +376,19 @@ Scrolling and Clipping Overflow: the 'overflow-x', 'overflow-y', and 'overflow'
 	is not ''overflow/visible'',
 	it creates a new <a>block formatting context</a> for its content.
 
-<h3 id="overflow-propagation">
-Overflow Value Propagation</h3>
 
-	UAs must apply the 'overflow-*' values
-	set on the root element to the <a>viewport</a>.
-	However,
-	when the root element is an [[!HTML]] <{html}> element
-	(including <a href="https://html.spec.whatwg.org/multipage/introduction.html#html-vs-xhtml">XML syntax for HTML</a>)
-	whose 'overflow' value is ''overflow/visible'' (in both axes),
-	and that element has a <{body}> element as a child,
-	user agents must instead apply the 'overflow-*' values
-	of the first such child element to the viewport.
-	The element from which the value is propagated must then have
-	a used 'overflow' value of ''overflow/visible''.
+<h3 id="static-media">
+Overflow in Print and Other Static Media</h3>
 
-	If ''overflow/visible'' is applied to the viewport,
-	it must be interpreted as ''overflow/auto''.
+	<p class="issue">
+		This specification should define useful behavior
+		for all values of 'overflow'
+		in static media (such as print).
+		Current implementation behavior is quite poor and
+		produces unexpected results when authors have not considered
+		what will happen when
+		the content they produce for interactive media
+		is printed.
 
 <h3 id="scrollbar-layout">
 Scrollbars and Layout</h3>
@@ -430,6 +426,24 @@ Scrolling Origin, Direction, and Restriction</h3>
 
 	The viewport uses the <a>principal writing mode</a> for these calculations.
 
+<h3 id="overflow-propagation">
+Overflow Viewport Propagation</h3>
+
+	UAs must apply the 'overflow-*' values
+	set on the root element to the <a>viewport</a>.
+	However,
+	when the root element is an [[!HTML]] <{html}> element
+	(including <a href="https://html.spec.whatwg.org/multipage/introduction.html#html-vs-xhtml">XML syntax for HTML</a>)
+	whose 'overflow' value is ''overflow/visible'' (in both axes),
+	and that element has a <{body}> element as a child,
+	user agents must instead apply the 'overflow-*' values
+	of the first such child element to the viewport.
+	The element from which the value is propagated must then have
+	a used 'overflow' value of ''overflow/visible''.
+
+	If ''overflow/visible'' is applied to the viewport,
+	it must be interpreted as ''overflow/auto''.
+
 <h2 id="max-lines">
 Limiting Visible Lines: the 'max-lines' property</h2>
 
@@ -509,18 +523,6 @@ Limiting Visible Lines: the 'max-lines' property</h2>
 	do not affect the position of the forced <a>region break</a>
 	introduced by the 'max-lines' property.
 
-<h2 id="static-media">
-Overflow in static media</h2>
-
-	<p class="issue">
-		This specification should define useful behavior
-		for all values of 'overflow'
-		in static media (such as print).
-		Current implementation behavior is quite poor and
-		produces unexpected results when authors have not considered
-		what will happen when
-		the content they produce for interactive media
-		is printed.
 
 
 Privacy and Security Considerations {#priv-sec}