diff options
| author | jdduke@chromium.org <jdduke@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-10 02:47:26 +0000 |
|---|---|---|
| committer | jdduke@chromium.org <jdduke@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-10 02:47:26 +0000 |
| commit | a3f1d98f5530f8e68fab9e601147240ea79cfb6e (patch) | |
| tree | 49e57ac96c5eaf0f0a9a2c55a8101ed515e6cc99 /chrome/chrome_debugger.gypi | |
| parent | 063854ec9dca4c3a460812c3eddf54eb7f9588dd (diff) | |
| download | chromium_src-a3f1d98f5530f8e68fab9e601147240ea79cfb6e.zip chromium_src-a3f1d98f5530f8e68fab9e601147240ea79cfb6e.tar.gz chromium_src-a3f1d98f5530f8e68fab9e601147240ea79cfb6e.tar.bz2 | |
Allow exclusive touchmove slop regions in the TouchEventQueue
Aura's current slop region is boundary exclusive, whereas Android's is boundary
inclusive. With the unified GR, both platforms will use a boundary inclusive
slop region, but until such time the TouchEventQueue should support either
model. Allow this distinction via a configurable TouchEventQueue::Config
parameter.
BUG=354763
Review URL: https://codereview.chromium.org/273933002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269496 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_debugger.gypi')
0 files changed, 0 insertions, 0 deletions