diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-01-12 20:38:49 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-01-12 20:38:49 +0000 |
| commit | 3f70c1e17d42cccd53e1b827d239c86d1ed701da (patch) | |
| tree | d1af746656d76471d38ae178375debdcb0a686ae /build | |
| parent | ab8089b5a8442d10b85fd12b40b8771c86c81b8d (diff) | |
| download | chromium_src-3f70c1e17d42cccd53e1b827d239c86d1ed701da.zip chromium_src-3f70c1e17d42cccd53e1b827d239c86d1ed701da.tar.gz chromium_src-3f70c1e17d42cccd53e1b827d239c86d1ed701da.tar.bz2 | |
Unhandled keyboard messages coming back from the host browser running ChromeFrame need to process
accelerators. Currently accelerators are processed by the focus manager. We already have code in browser_view
to process unhandled keyboard messages coming back from the renderer. Moved this code to a new class
UnhandledKeyboardEventHandler which maintains state about whether the next character event has to be ignored, etc.
This class is now used by BrowserView and the ExternalTabContainer to process unhandled keyboard messages.
To support accelerators in ChromeFrame, the ExternalTabContainer needs to implement an Accelerator target. I also
added a minimal accelerator table for Chromeframe in the chrome_dll.rc and chrome_dll_resource.h files.
This fixes bug http://code.google.com/p/chromium/issues/detail?id=31672
Bug=31672
Review URL: http://codereview.chromium.org/536023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36037 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions