diff options
| author | mma.public@gmail.com <mma.public@gmail.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-03 22:12:35 +0000 |
|---|---|---|
| committer | mma.public@gmail.com <mma.public@gmail.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-03 22:12:35 +0000 |
| commit | 38ba5bd7a0c7770e95aea6619174a953e5d92796 (patch) | |
| tree | d02998d4539a1f889075757e25bfbf1855495d79 /chrome/browser/ui/gtk/first_run_dialog.h | |
| parent | bf1bc621e881b18db2c0e70b7f0b6e46b0a2fc52 (diff) | |
| download | chromium_src-38ba5bd7a0c7770e95aea6619174a953e5d92796.zip chromium_src-38ba5bd7a0c7770e95aea6619174a953e5d92796.tar.gz chromium_src-38ba5bd7a0c7770e95aea6619174a953e5d92796.tar.bz2 | |
Modifies the event handler for WM_APPCOMMAND events to return TRUE if the event was handled. Previously it returned 0 causing the event to bubble up to the DefWndProc, which would synthesize keypresses appropriate for the event and cause it to effectively be handled twice.
This should fix double handling of events for people with devices that generate WM_APPCOMMAND messages (tablets, Logitech mice, etc...)
BUG=19672
TEST=See various cases reported on bug
Review URL: http://codereview.chromium.org/6901076
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83975 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/ui/gtk/first_run_dialog.h')
0 files changed, 0 insertions, 0 deletions