Skip to content

Commit a689c87

Browse files
committed
[css-scroll-snap] Fix linking error
1 parent 7576dd1 commit a689c87

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

css-scroll-snap/Overview.bs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -405,8 +405,8 @@ Scroll Snapping Coordinates: the 'scroll-snap-points-x' and 'scroll-snap-points-
405405
Coordinates specified by 'scroll-snap-points-x' and 'scroll-snap-points-y'
406406
are not affected by 'scroll-snap-padding'/'scroll-snap-destination'.
407407

408-
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?
409-
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.)
408+
Issue: Should we add <css>start-edge</css> and <css>end-edge</css> keywords here, so that the start and end of the scrollable area can be defined as reachable?
409+
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 <css>start</css> or <css>end</css> here.)
410410

411411
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"?
412412

0 commit comments

Comments
 (0)