DescriptionRevert of Re-target wheel events only when a new scroll sequence has started. (patchset #7 id:220001 of https://codereview.chromium.org/2928793003/ )
Reason for revert:
Flaky on Android Tests buildbot.
First breaking build: https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests/builds/42822
Original issue's description:
> Re-target wheel events only when a new scroll sequence has started.
>
> In RouteMouseWheelEvent, when a wheel event with phase began arrives,
> find the target for wheel event. While no wheel with phase end has
> arrived (during a scroll sequence) send the wheel events to the saved
> target.
>
> In EventHandler, do the same targetting to dispatch the events to js.
>
> BUG=526463
> TEST=WheelScrollLatchingBrowserTest.WheelEventTarget,
> WheelScrollLatchingDisabledBrowserTest.WheelEventTarget
>
> Review-Url: https://codereview.chromium.org/2928793003
> Cr-Commit-Position: refs/heads/master@{#480052}
> Committed: https://chromium.googlesource.com/chromium/src/+/8aa8c38005ee36bc441138c81a5cf165fb6514a5
TBR=bokan@chromium.org,tdresser@chromium.org,sahel@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=526463
Review-Url: https://codereview.chromium.org/2943183002
Cr-Commit-Position: refs/heads/master@{#480171}
Committed: https://chromium.googlesource.com/chromium/src/+/622b6164229bea82e61b916f5d9d41bc02b3488a
Patch Set 1 #Messages
Total messages: 6 (3 generated)
|