-
sadrul@chromium.org authored
It is possible that a window starts doing synchronous touch-event handling after doing asynchronous handling for some time. As a result, these sync events may be processed before the acks for the queued asynchronous events have been processed. This results in unexpected behaviour. So in such cases, queue up the synchronous events so that they get processed only after the asynchronous events are processed. BUG=139339, 134486 Review URL: https://chromiumcodereview.appspot.com/10825323 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151361 0039d316-1c4b-4281-b951-d872f2087c98
be979714