diff options
| author | oshima@chromium.org <oshima@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-01-05 20:43:41 +0000 |
|---|---|---|
| committer | oshima@chromium.org <oshima@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-01-05 20:43:41 +0000 |
| commit | a9c060ca3ef4c5834955e94fe65bca94fb47c6a6 (patch) | |
| tree | 4abc33f6679d789ff09a23dd92d564024b58874b /printing/backend | |
| parent | 24845d70f3c481caa231cc24322927f636f3acd7 (diff) | |
| download | chromium_src-a9c060ca3ef4c5834955e94fe65bca94fb47c6a6.zip chromium_src-a9c060ca3ef4c5834955e94fe65bca94fb47c6a6.tar.gz chromium_src-a9c060ca3ef4c5834955e94fe65bca94fb47c6a6.tar.bz2 | |
AURA/X11: Handle VKEY_MENU accelerator on content area
-Moved the code to handle vkey_menu to focus manager.
-Unify the code between win/aura/gtk to handle unhandled web keyevent. We were using different code path for unhandled web keyboard for regular page and login. This should fix this issue also.
-Improved focus test not to use fixed wait. This should also speedup the test a bit.
-Removed OmniboxViewViews tests that runs only on views/gtk. This is no longer supported and we can re-enable for win when ready.
BUG=99861,106998, 108480, 108459
TEST=manual: set focus to content area and hit alt key. the focus should be set to wrench menu on release.
Review URL: http://codereview.chromium.org/8907029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116541 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'printing/backend')
0 files changed, 0 insertions, 0 deletions