Confirmed users
23
edits
WebAPI/BrowserAPI/KeyboardEvent: Difference between revisions
→Plan of Change
| Line 332: | Line 332: | ||
=== Plan of Change === | === Plan of Change === | ||
In patch of https://bugzilla.mozilla.org/show_bug.cgi?id=989198, Gina will keep both mozChromeEvents and new KeyboardEvents dispatching at the same time. But we only need to listen to one of them in Gaia. | |||
==== Part 1 ==== | |||
The state objects in hardware_buttons.js and software_button_manager.js all have dependency on low level input event names listed above. | |||
In this part, we stop listening to 'mozChromeEvent' and start listening to 'mozbrowserbeforekeydown' and mozbrowserbeforekeyup' event, and do a translation in handleEvent of hardware_buttons.js. | |||
Translations are as follows: | |||
[[File:Mozbrowserkeyxxx translate.png|800px|frameless|center]] | |||
==== Part 2 ==== | |||
=== Bugs === | === Bugs === | ||