Bug 144706 - Scroll-snap 'elements' code path is not tested
Summary: Scroll-snap 'elements' code path is not tested
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-06 12:44 PDT by Brent Fulgham
Modified: 2020-10-16 09:44 PDT (History)
2 users (show)

See Also:


Attachments
3x3 grid of large elements in the mainframe with scroll snap coordinates. (1.09 KB, text/html)
2015-06-26 22:23 PDT, Wenson Hsieh
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Fulgham 2015-05-06 12:44:58 PDT
We need to build a set of tests that exercise the 'elements' target for scroll-snap-points. Right now, this code is only rarely exercised and could easily be broken as we do more development.
Comment 1 Wenson Hsieh 2015-06-26 22:20:27 PDT
While working on https://bugs.webkit.org/show_bug.cgi?id=142523, I just discovered that  scroll snapping with elements in the mainframe for OSX seems to be broken on the current tip. I've added a test case that exhibits this issue.
Comment 2 Wenson Hsieh 2015-06-26 22:23:07 PDT
Created attachment 255692 [details]
3x3 grid of large elements in the mainframe with scroll snap coordinates.

Scrolling in the mainframe of this page should trigger scroll snapping.
Comment 3 Martin Robinson 2020-10-16 09:44:57 PDT
I did some digging through the history of the specification and I think that all captured snap points exercise the "elements" path. I have also recently imported all of the WPT scroll-snap tests, so I think we have some decent test coverage now. I'm going to resolve bug, but feel free to reopen.