Revision 343fd25cd72c64ed30da54b650220cca7338cd57 authored by Sandra Sun on 14 March 2018, 17:24:07 UTC, committed by Blink WPT Bot on 14 March 2018, 18:11:13 UTC
According to spec, https://www.w3.org/TR/css-scroll-snap-1/#snap-scope we should only consider the snap points of visible snap areas. This patch implements the visibility requirement by adding a field of visible region for each snap point. It also handles the case of visibility conflict when snapping to two axes individually. Bug: 778257 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I7a3d2aa6b9c1293df3f05118152f105fa3265d29 Reviewed-on: https://chromium-review.googlesource.com/814874 Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Ali Juma <ajuma@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#543111}
1 parent ec54ac4
File | Mode | Size |
---|---|---|
resources | ||
cross_origin.html | -rw-r--r-- | 1.2 KB |
server_timing_header-parsing.html | -rw-r--r-- | 1.7 KB |
test_server_timing.html | -rw-r--r-- | 1.6 KB |
test_server_timing.html.sub.headers | -rw-r--r-- | 80 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...