You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that span the <a>scrollable area</a> in the appropriate axis,
375
+
starting from the <a>start</a> edge of the <a>scrollable area</a>
376
+
and spanning across every <<length>> throughout the <a>scrollable area</a>.
375
377
376
378
Negative values are invalid.
377
379
User agents must define a UA-defined minimum <<length>> greater than 0
378
380
(recommended ''1px''),
379
-
and clamp the computed value to that minimum.
381
+
and clamp the used value to that minimum.
380
382
</dl>
381
383
382
384
Coordinates specified by 'scroll-snap-points-x' and 'scroll-snap-points-y'
383
385
are not affected by 'scroll-snap-padding'/'scroll-snap-destination'.
384
386
387
+
Issue: Or should they also be affected by 'scroll-snap-padding'?
388
+
Also we're effectively assuming start-alignment here, is that what we want?
389
+
Or do we want to allow other alignments?
390
+
385
391
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?
386
392
This would be good for e.g. maps.
387
393
(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.)
@@ -395,7 +401,7 @@ Scroll Snapping Coordinates: the 'scroll-snap-points-x' and 'scroll-snap-points-
395
401
Element-based Snapping {#element}
396
402
======================
397
403
398
-
Scroll Snapping Area: the 'scroll-snap-area' property {#the-scroll-snap-area}
404
+
Scroll Snapping Area: the 'scroll-snap-area' property {#scroll-snap-areas}
0 commit comments