Bug 145330 - Scroll-snap points should be triggered during programmatic scroll
Summary: Scroll-snap points should be triggered during programmatic scroll
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2015-05-22 17:20 PDT by Brent Fulgham
Modified: 2015-09-24 11:11 PDT (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Brent Fulgham 2015-05-22 17:20:27 PDT
I've recently made a set of bug fixes that help the engine keep track of the current snap point, even after programmatic scrolls.

For proper behavior, when a programmatic scroll occurs that will take us close to a snap point, we should drive an animation to that snap point. If the programmatic scroll was not sufficient to take us past, say, the midpoint between two snap points, we should roll back to the original snap point once the scroll operation completes.

However, this would break manually animated scrolling operations.

One possible answer to this problem is to say "Don't try to combine scroll-snap points and programmatic scrolling."
Comment 1 Brent Fulgham 2015-06-19 14:37:00 PDT
This is currently under discussion in the css working group. The current thought is that we should not invoke scroll snap points for programmatic scrolls, but we should add a 'snap' element to the ScrollOptions dictionary.
Comment 2 Radar WebKit Bug Importer 2015-06-19 14:37:26 PDT