diff options
| author | cpu@chromium.org <cpu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-02-02 00:19:45 +0000 |
|---|---|---|
| committer | cpu@chromium.org <cpu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-02-02 00:19:45 +0000 |
| commit | 11e45efce9cc17e1b2b76e6a636cc63b2c021324 (patch) | |
| tree | 34ca44e268f04034943a6ef2718874f1ba903ab7 /chrome_frame/utils.cc | |
| parent | c356dc8972b1b0578e3e016de4ee56a62a5a02aa (diff) | |
| download | chromium_src-11e45efce9cc17e1b2b76e6a636cc63b2c021324.zip chromium_src-11e45efce9cc17e1b2b76e6a636cc63b2c021324.tar.gz chromium_src-11e45efce9cc17e1b2b76e6a636cc63b2c021324.tar.bz2 | |
Allow accelerators to work on Windows Ash mode
We had 3 issues
1- NativeKeyboardEvent had skip_in_browser = true hardcoded so
when the event comes back from the renderer we ignore it
2- NativeKeyboardEvent was constructed in a way that ctrl-f would have
the wrong keycode
3- The unhandled keyboard event handler assumed that the ui event had
an inner native MSG which is not the case for ash so we would crash
on say F10.
BUG=173572
TEST=see bug
Review URL: https://codereview.chromium.org/12082112
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180210 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/utils.cc')
0 files changed, 0 insertions, 0 deletions