<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:ap@webkit.org" title="Alexey Proskuryakov <ap@webkit.org>"> <span class="fn">Alexey Proskuryakov</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Some scroll snap overflow tests are flaky"
href="https://bugs.webkit.org/show_bug.cgi?id=148408">bug 148408</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>bdakin@apple.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Some scroll snap overflow tests are flaky"
href="https://bugs.webkit.org/show_bug.cgi?id=148408#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Some scroll snap overflow tests are flaky"
href="https://bugs.webkit.org/show_bug.cgi?id=148408">bug 148408</a>
from <span class="vcard"><a class="email" href="mailto:ap@webkit.org" title="Alexey Proskuryakov <ap@webkit.org>"> <span class="fn">Alexey Proskuryakov</span></a>
</span></b>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>