Re: [snappoints] behavior when the maximum scroll position isn't a snap point

• From: François REMY <francois.remy.dev@outlook.com>
• Date: Sat, 30 Aug 2014 11:18:56 +0200
• To: "Edward O'Connor" <eoconnor@apple.com>, <www-style@w3.org>
• Message-ID: <DUB130-DS4BE96EC3EED9688F58B5EA5D80@phx.gbl>

> What should engines do when scrolling to the edge of a container with
> snap points if there isn’t a snap point at the maximum scroll position
> in the container? In this case, some of the content might be unreachable
> by scrolling—when scrolling toward the end, the scroll offset would
> animate to the closest snap point, which is behind the scroll offset,
> causing it to “bounce back” from the end. Is this even a problem, or is
> this effect something authors might actually want?
>
> One way to prevent this would be to add “implicit” snap points at the
> ends of the container, so all content in the container can be reached by
> scrolling.
>
> What do you think?

I've no particular opinion on this, but bouncing back from an end may be a 
feature, actually, if the aim is to implement a "pull-to-refresh" section 
after the content. 

Received on Saturday, 30 August 2014 09:19:19 UTC