diff options
| author | mohsen <mohsen@chromium.org> | 2016-01-27 14:22:46 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-01-27 22:23:37 +0000 |
| commit | 0df5837131a55ff6560a80b181ef90e620ea8092 (patch) | |
| tree | ea2775b30f02f26db25a15c4ac4aa74ff3ce5158 /components/test_runner | |
| parent | 404d443df35096d2ea5d35644654df41c71812dc (diff) | |
| download | chromium_src-0df5837131a55ff6560a80b181ef90e620ea8092.zip chromium_src-0df5837131a55ff6560a80b181ef90e620ea8092.tar.gz chromium_src-0df5837131a55ff6560a80b181ef90e620ea8092.tar.bz2 | |
Remove MenuMessagePumpDispatcher
MenuMessagePumpDispatcher is used on Windows to handle keyboard events
and some other events in menu message loops. In order to have fully
async menus, we need to get rid of it. Instead, we can use
MenuKeyEventHandler which is used on Chrome OS and Linux with some
modifications. Following are messages that are handled in
MenuMessagePumpDispatcher and how they can be handled after removing
this class:
- WM_KEYDOWN: This will be handled in MenuKeyEventHandler::OnKeyEvent.
- WM_CHAR: This is used to handle "translated" characters for mnemonics
according to the active keyboard layout. We can achieve this in
MenuKeyEventHandler by using event->GetCharacter() instead of
ui::DomCodeToUsLayoutCharacter().
- WM_SYSKEYDOWN: This happens when Alt or F10 keys are pressed
(according to MSDN). We can handle these keys in MenuKeyEventHandler.
- WM_CANCELMODE: This is already handled in
ActivationChangeObserverImpl::OnCancelMode() which is used in
MenuMessageLoopAura.
BUG=564255,566019
Review URL: https://codereview.chromium.org/1625313002
Cr-Commit-Position: refs/heads/master@{#371894}
Diffstat (limited to 'components/test_runner')
0 files changed, 0 insertions, 0 deletions