[css-scroll-snap] Tweaks to Choosing Snap Points per <https://lists.w3.org/Archives/Public/www-style/2016Jun/0020.html>

Author: fantasai

css-scroll-snap/Overview.bs

@@ -764,14 +764,14 @@ Choosing Snap Positions {#choosing}
         <a>snap positions</a> should be penalized in the selection process
         according to the amount of other-axis scrolling they would cause.
 
-    * <a>Snap positions</a> should be ignored if their elements are far outside of the “corridor”
-        that the <a>snapport</a> defines as it moves through the <a>scrollable overflow region</a>
+    * In order to prevent a far-offscreen element
+        from having difficult-to-understand effects
+        on the scroll position,
+        <a>snap positions</a> should be ignored if their elements are far outside of the “corridor”
+        that the <a>snapport</a> defines as it moves through the <a>scrollable overlow region</a>
         during an <a>inertial scroll</a>,
         or a hypothetical “corridor” in the direction of a <a>directional scroll</a>,
         or the <a>snapport</a> after an <a>explicit scroll</a>.
-        (This is to prevent a far-offscreen element
-        from having difficult-to-understand effects
-        on the scroll position.)
 
     * User agents <em>must</em> ensure that a user can “escape” a <a>snap position</a>,
         regardless of the scroll method.
@@ -788,7 +788,8 @@ Choosing Snap Positions {#choosing}
         (This implies that a <a>directional scroll</a> must always ignore the starting <a>snap positions</a>.)
 
     * If a page is navigated to a fragment that defines a target element
-        (one that would be matched by '':target''),
+        (one that would be matched by '':target'',
+        or the target of {{Element/scrollIntoView()}}),
         and that element defines some <a>snap positions</a>,
         the user agent should <a>snap</a> to one of that element's <a>snap positions</a>.
         The user agent may do this even when the <a>scroll container</a> has ''scroll-snap-type: none''.