Do not coalesce events received before and after a kRelativeMotionEvent
When a WebCoalescedInputEvent is getting built from individual input events by the renderer, it looks for events that can be coalesced together. If there is a kRelativeMotionEvent in the queue, existing logic is to skip it and coalesce the next events. In case of a pointer lock, kRelativeMotionEvent is sent during a cursor recenter. Events before kRelativeMotionEvent and events after kRelativeMotionEvent differ by a big margin and should not be coalesced together. This patch correctly stops coalescing when a kRelativeMotionEvent is seen thereby avoiding incorrect bigdeltas from being sent to the DOM. Bug: 1066544 Change-Id: I1a38391e41f4d0bc11ec67c88e3df1d321bc15bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226479Reviewed-by:Ella Ge <eirage@chromium.org> Reviewed-by:
Mustaq Ahmed <mustaq@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by:
Vincent Scheib <scheib@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#774654}
Showing
Please register or sign in to comment