[css-snappoints] Merging element snap points with snap points from repeat()

From Majid:

> I understand how making elements and repeat mutually can help with a
> simpler syntax but are there no good use case for using both at the same
> time? Perhaps a map that snaps at 100% intervals and city centers?

So far no good examples.  Snapping a map at 100% intervals wouldn't make sense since it's not a paginated scenario, plus mixing it with city center snap points would just make it appear to the end-user as if the snapping "missed the city" at random.

I don't have a strong opinion here but with no supporting scenarios I'd rather take the simpler route unless/until we have a hypothetical customer at least.

> Also, any ideas on how we are going to handle specification of scrollable
> area start and ends as snap points? I can see something like:
>               scroll-snap-points-x: *start* repeat(100%) *end*
> 
> These snap points cannot be be mutually exclusive with either elements or
> repeat. If that is going to be handled using a space-delimited syntax then
> allowing the repeat in the mix should not make thing anymore complicated.

I've spent less time thinking about specialized start/end snap points since we haven't really heard requests for them.  In theory it sounds like functionality you'd expect, but in practice I haven't really seen cases that would require it.  Authors using the interval syntax typically have content that is an even multiple of their interval size, so *start* and *end* are already snapped to without explicitly specifying them.  For elements it's somewhat difficult to imagine a scenario where the author wants to snap to elements, but also to the start and/or end despite not having an element there.

Similar to above I don't have a strong opinion either way since I don't have a supporting scenario, but I'd prefer a leaner spec if there's not a compelling reason to ask implementers to take on extra work.

Thanks,
-Matt

Received on Wednesday, 29 July 2015 20:31:47 UTC