Radar link: <rdar://problem/17283505>
Implement CSS snap points according to the (not yet final) W3C spec here: http://dev.w3.org/csswg/css-snappoints/
See bug-issues for more details.
(In reply to comment #0)
> Radar link: <rdar://problem/17283505>
> Implement CSS snap points according to the (not yet final) W3C spec here: http://dev.w3.org/csswg/css-snappoints/
> See bug-issues for more details.
^^^ that's *sub*-issues, not bug-issues
First sub-issue: https://bugs.webkit.org/show_bug.cgi?id=134301
Second subissue: exposing trackpad scrolling phases https://bugs.webkit.org/show_bug.cgi?id=134283
(In reply to comment #4)
[Correction] Second sub-issue is https://bugs.webkit.org/show_bug.cgi?id=135195, not this page.
Created attachment 236686 [details]
Basic scroll-snapping examples
Contains two web pages that demonstrate basic examples of snap scrolling. iphone.html shows a vertically scrolling overflow div that fills the entire window and has a snap point at the top of every image. itunes.html shows three divs: the first scrolls horizontally with images snapping to the left edge; the second also scrolls horizontally, but has images snapping to the center; the last example shows 2D scrolling, with snap points on both axes at every image.
List of known issues with CSS snap points implementation:
- Rename the CSS_SCROLL_SNAP feature flag to CSS_SNAP_POINTS.
- Make WKWebView set deceleration to fast when didCommitLayerTree is called, rather than when scrolling will begin dragging.
- Account for insets on the iOS mainframe.
- Improve Mac snapping animations (also, improve their performance)
- In the spec, the repeat value begins counting from the "last point." We need to clarify what this means -- currently, the implementation starts counting from the furthest point, which would not be correct if the list of snap points is not sorted and our interpretation of "last point" is the last point specified by the user.
- Clarify what the expected behavior is when a snap point moves, disappears, or is added to the snap scrolling container.
Can we close this now?
Removing dependency on 203684 as it is now part of the metabug at: issue 221461.
I think it makes sense to close this issue. We have the metabug at https://bugs.webkit.org/show_bug.cgi?id=218115 to track remaining implementation / compatability issues and then there are also quite a few remaining issues related to scroll snap behavior in Bugzilla in general.