[css-scroll-snap] Align scroll-snap-points-x/y with existing draft, mark start/end as issue.

Author: fantasai

css-scroll-snap/Overview.bs

@@ -339,7 +339,7 @@ Scroll Snapping Coordinates: the 'scroll-snap-points-x' and 'scroll-snap-points-
 
 	<pre class="propdef">
 	Name: scroll-snap-points-x, scroll-snap-points-y
-	Value: none | [ start || end || repeat(<length>) ]
+	Value: none | repeat(<length>)
 	Initial: start end
 	Applies to: <a>scroll containers</a>
 	Inherited: no
@@ -359,16 +359,6 @@ Scroll Snapping Coordinates: the 'scroll-snap-points-x' and 'scroll-snap-points-
 			No <a>snap positions</a> are defined by this <a>scroll container</a>.
 			Contained elements may still define <a>snap positions</a> on this <a>scroll container's</a> behalf.
 
-		<dt><dfn>start</dfn>
-		<dd>
-			The <a>start</a> edge of the <a>scrollable area</a> in the appropriate axis
-			is a <a>snap position</a>.
-
-		<dt><dfn>end</dfn>
-		<dd>
-			The <a>end</a> edge of the <a>scrollable area</a> in the appropriate axis
-			is a <a>snap position</a>.
-
 		<dt><dfn>repeat(<<length>>)</dfn>
 		<dd>
 			Defines <a>snap position</a> that span the <a>scrollable area</a> in the appropriate axis,
@@ -382,7 +372,8 @@ Scroll Snapping Coordinates: the 'scroll-snap-points-x' and 'scroll-snap-points-
 
 	Issue: We changed the initial value to make it so that the start and end of the scrollable area are always reachable and snappable.
 
-	Issue: See <a href="https://lists.w3.org/Archives/Public/www-style/2015Jul/0453.html">Matt Rakow's take</a> on not having ''start'' or ''end'' here.
+	Issue: Should we add ''start-edge'' and ''end-edge'' keywords here, so that the start and end of the scrollable area can be defined as reachable?
+	This would be good for e.g. maps. (See <a href="https://lists.w3.org/Archives/Public/www-style/2015Jul/0453.html">Matt Rakow's take</a> on not having ''start'' or ''end'' here.)
 
 	Issue: It was <a href="https://lists.w3.org/Archives/Public/www-style/2015Jul/0453.html">suggested</a> that repeat() be mutually exclusive with element-based snap positions. Is there a better way to integrate this than having the initial value here be "elements"?