[css-scroll-snap-2] rearranging interaction sections

Author: argyleink

css-scroll-snap-2/Overview.bs

@@ -130,7 +130,7 @@ The 'scroll-start' property {#scroll-start}
 
 	<pre class="propdef shorthand">
 	Name: scroll-start
-	Value: [ auto | start | end | center | <<length-percentage>> ]{1,2}
+	Value: [ auto | start | end | center | left | right | top | bottom | <<length-percentage>> ]{1,2}
 	</pre>
 
 	This property is a shorthand property that sets all of the scroll-start-* longhands in one declaration.
@@ -160,6 +160,36 @@ The 'scroll-start' property {#scroll-start}
 			Equivalent to ''0%'', ''50%'', and ''100%'', respectively.
 	</dl>
 
+<h4 id="display-none-behavior">Interaction with ''display: none'' and initial creation</h4>
+  Same behavior that animations follow with <a href="#first-layout">first layout</a>.
+
+<h4 id="slow-page-load-behavior">Slow page loading or document streaming behavior</h4>
+  TODO
+
+<h4 id="fragment-navigation-behavior">Interaction with ''fragment navigation''</h4>
+  TODO
+  If the scrollport has a in-page '':target'' via a URL fragment or a previous scroll position, then ''scroll-start'' is unused. Existing target logic should go unchanged. This makes ''scroll-start'' a soft request in the scroll position resolution routines.  
+
+<h4 id="place-content-behavior">Interaction with ''place-content''</h4>
+  TODO  
+  Side note: While ''place-content'' can make a scroller appear to start in the center
+  or end, no browser supports it and it appears complicated to resolve.
+
+<h4 id="find-in-page-behavior">Interaction with "find in page"</h4>
+  TODO
+
+<h4 id="scroll-snap-container-behavior">Interaction ''scroll-snap'' containers</h4>
+  This effectively will layout and start scroll at the snapped child, thus negating / cancelling ''scroll-start''. ''scroll-start'' will only work if nothing else has effected the scroll position.
+
+<h4 id="nested-scrollers">Nested scrollers with ''scroll-start''</h4>
+  Should follow patterns that scroll snap has set.
+
+<h4 id="toggling-display-none">Interaction when ''display'' is toggled</h4>
+  Same behavior that animations follow with ''first layout''.
+
+<h4 id="rtl">Interaction with RTL and LTR</h4>
+  Logical properties are offered for length offsets that should be flow relative. Furthermore, the ''end'' and ''start'' keywords are always logical.
+
 The 'scroll-start-target' property {#scroll-start-target}
 -------------------------------------------
 
@@ -180,8 +210,8 @@ The 'scroll-start-target' property {#scroll-start-target}
     <dd>Element is not a ''scroll-start-target''.
     <dt><dfn>auto</dfn>
     <dd>Element is used to calculate the ''scroll-start'' position, 
-    taking into account ''scroll-padding'' 
-    as if the element was a ''scroll-snap'' target.
+    taking into account ''scroll-padding'' or ''scroll-margin'' ,
+    same as a ''scroll-snap'' target.
   </dl>
 
 Styling Snapped Items {#todo}
@@ -219,7 +249,7 @@ More specific options are defined as follows:
 Note: <a href="https://github.com/w3c/csswg-drafts/issues/6985#issuecomment-1049036401">Issue #6985</a><br>
 Need to figure out resolution of the initial frame.
 
-Snap Events {#todo}
+Snap Events {#snap-events}
 ===================
 
 <!--
@@ -232,7 +262,7 @@ Snap Events {#todo}
 ████████    ███    ████████ ██    ██    ██     ██████
 -->
 
-{{snapChanged}} and {{snapChanging}} {#todo}
+{{snapChanged}} and {{snapChanging}} {#snapchanged-and-snapchanging}
 --------------------------------------------
 
 	CSS scroll snap points are often used as a mechanism to
@@ -256,53 +286,6 @@ Snap Events {#todo}
 				<td>{{scroll!!event}}
 	</table>
 
-<!-- BIG TEXT: INTERACTIONS -->
-
-Interactions with:
-==================
-
-The next sections outline interactions with other specs and scroll position effecting scenarios.
-
-''scroll-padding'' and ''scroll-margin''
-----------------------------------------
-
-    If the scrollport has a in-page '':target'' via a URL fragment or a previous scroll position, then ''scroll-start'' is unused. Existing target logic should go unchanged. This makes ''scroll-start'' a soft request in the scroll position resolution routines.
-
-''fragment navigation''
------------------------
-
-    If the scrollport has a in-page '':target'' via a URL fragment or a previous scroll position, then ''scroll-start'' is unused. Existing target logic should go unchanged. This makes ''scroll-start'' a soft request in the scroll position resolution routines.
-
-''scrollTo()'' options
-----------------------
-
-    TODO
-
-a ''scroll-snap'' container with only 1 snap child
---------------------------------------------------
-
-    This effectively will layout and start scroll at the snapped child, thus negating / cancelling ''scroll-start''. ''scroll-start'' will only work if nothing else has effected the scroll position.
-
-nested scrollers
-----------------
-
-    Should follow patterns that scroll snap has set.
-
-''display'' is toggled
-----------------------
-
-    Same behavior that animations follow with ''first layout''.
-
-RTL/LTR
--------
-
-    Logical properties are offered for length offsets that should be flow relative. Furthermore, the ''end'' and ''start'' keywords are always logical.
-
-''place-content''
------------------
-
-    TODO
-
 <!--
 ██        ███████  ██    ██  ██████   ██     ██    ███    ██    ██ ████████   ██████
 ██       ██     ██ ███   ██ ██    ██  ██     ██   ██ ██   ███   ██ ██     ██ ██    ██