148408 2015-08-24 17:28:26 -0700 Some scroll snap overflow tests are flaky 2016-12-01 10:36:56 -0800 1 1 1 Unclassified WebKit Tools / Tests Other Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=148407 https://bugs.webkit.org/show_bug.cgi?id=165196 P2 Normal --- 1 ap webkit-unassigned bdakin bfulgham simon.fraser wenson_hsieh oldest_to_newest 1120472 0 ap 2015-08-24 17:28:26 -0700 Some scroll snap tests have become flaky when asynchronous. This is reproducible locally when repeating them many times, e.g. "--repeat 500 -f". tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-borders.html tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-overflow.html tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-rotated.html tiled-drawing/scrolling/scroll-snap/scroll-snap-mandatory-padding.html 1120475 1 ap 2015-08-24 17:35:27 -0700 Also tiled-drawing/scrolling/scroll-snap/scroll-snap-iframe.html Marked as flaky in r188899. 1121339 2 ap 2015-08-27 10:18:03 -0700 There is a clear opportunity for a race between the end of regular scroll and the beginning of momentum scroll. Some potential approaches: - tell eventSender.callAfterScrollingCompletes whether it needs to wait for momentum scroll; - this could be automagic, because all scrolls are started via eventSender functions, and we do post the momentum scrolling events before calling eventSender.callAfterScrollingCompletes; - or it may be possible to have an eventSender function that both finishes regular scroll and starts a momentum one, or some other higher level description of a scroll that we'd use with eventSender. That way, we would keep the knowledge that there is a momentum scroll coming for longer.