diff options
| author | boliu <boliu@chromium.org> | 2016-03-10 23:02:14 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-03-11 07:03:13 +0000 |
| commit | de5b75b1ccd0ef7f478318d805b3ba1c8ebf7130 (patch) | |
| tree | 393ff97cfa98eda6ae12d59381dc0a71dbf22091 /content/zygote | |
| parent | a2e46e0ffc404d3168c0af4c3b89d8ae5475cc3d (diff) | |
| download | chromium_src-de5b75b1ccd0ef7f478318d805b3ba1c8ebf7130.zip chromium_src-de5b75b1ccd0ef7f478318d805b3ba1c8ebf7130.tar.gz chromium_src-de5b75b1ccd0ef7f478318d805b3ba1c8ebf7130.tar.bz2 | |
sync compositor: Merge input path with chrome
Use chrome's async input delivery path in Android WebView. See bug
for potential incompatibility risk. Existing code path is not removed
in case compatibility is an issue.
Refactor out ui::SynchronousInputHandlerProxy parts from
InputHandlerManagerClient into a separate interface so that sync
compositor can use SynchronousInputHandlerProxy even without
routing input synchronously. Then just stop filtering input events in
sync compositor, hook up overscroll, and everything just works.
Tests:
testNoSpuriousOverScrolls requires synchronous input to maintain
the property that a single scroll call happens. Asynchronously the
test is not valid
AwContents.zoomIn is no longer synchronous which breaks
testPinchZoomUpdatesScrollRangeSynchronously. Can fix this
independently if this becomes a problem later.
BUG=545628
Review URL: https://codereview.chromium.org/1620053002
Cr-Commit-Position: refs/heads/master@{#380563}
Diffstat (limited to 'content/zygote')
0 files changed, 0 insertions, 0 deletions