Route input-related IPCs through compositor thread filter to preserve order
The compositor thread input filter redirects some IPC messages in the render process to the compositor thread for handling in order to accelerate scrolling, pinch zooming, and related gestures. IPC messages that the compositor thread cannot handle are redirected to the main thread for normal processing. This thread hop can result in the IPC messages being received on the render process main thread in a different order than they were sent from the browser. This can break things for input-related messages, for instance changing the order of a MouseCaptureLost and MouseUp event can result in the mouse up not being delivered to the capturing element. This forces a compositor thread hop to preserve order for a set of IPC types that appear (mostly by inspection and guessing) to need their order preserved relative to input events. BUG=233365,231532 Review URL: https://chromiumcodereview.appspot.com/14328027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195329 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment