diff options
| author | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-17 17:31:58 +0000 |
|---|---|---|
| committer | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-09-17 17:31:58 +0000 |
| commit | db9e74fd1be6be0f838cc3dd8400f396ee70a90c (patch) | |
| tree | d437e7c761f4e451d3cdaa50e669232e0a9090b4 /google_apis | |
| parent | ad72280a8fbf5c7594ee1cb2f5f17d9634ffe031 (diff) | |
| download | chromium_src-db9e74fd1be6be0f838cc3dd8400f396ee70a90c.zip chromium_src-db9e74fd1be6be0f838cc3dd8400f396ee70a90c.tar.gz chromium_src-db9e74fd1be6be0f838cc3dd8400f396ee70a90c.tar.bz2 | |
Forward Capture.
This one is a little trickier, since there are two capture concepts in play:
- aura capture, used by the event dispatch logic in RootWindow to figure out where to send mouse drag events
- win32 capture, used by windows to determine where to send subsequent mouse events.
NativeWidgetPrivate::Set/Get/HasCapture are implemented in NativeWidgetAura setting only the first type, since that's all that's relevant in ash-land, where you don't need to track mouse events outside the HWND that is the RootWindowHost.
Not-so for Desktop Aura, so we need to set native capture too.
Capture can move within the aura::Windows in the RootWindowHost, but regardless we must always keep capture of the HWND associated with the in sync.
BUG=146077
R=scottmg@chromium.org
Review URL: https://codereview.chromium.org/10907258
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157144 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'google_apis')
0 files changed, 0 insertions, 0 deletions