Confirmed users
478
edits
User:Timdream/InputMethod API with hardware keyboard: Difference between revisions
Jump to navigation
Jump to search
User:Timdream/InputMethod API with hardware keyboard (view source)
Revision as of 07:22, 22 October 2013
, 22 October 2013→Idea
Janjongboom (talk | contribs) |
(→Idea) |
||
| Line 15: | Line 15: | ||
*** A: [Tim] If that's the case we would be sending three <code>HardwareKeyboardEvent</code> events to represent 3 keyboard events. Which is good if the keyboard app requires finer control (Luke mentioned that possibility to me). | *** A: [Tim] If that's the case we would be sending three <code>HardwareKeyboardEvent</code> events to represent 3 keyboard events. Which is good if the keyboard app requires finer control (Luke mentioned that possibility to me). | ||
** Q: What should <code>unblock(false)</code> do? Send the queued events to content? Could it queue more than one key events? | ** Q: What should <code>unblock(false)</code> do? Send the queued events to content? Could it queue more than one key events? | ||
*** A: | *** A: [Tim] Implementation should send the event, previous blocked, to content. When an event is blocked, all the follow-up events should be queued and be handled in sequence when the event is eventually unblocked. | ||
*janjongboom | *janjongboom | ||
** Q: apc.io already is working on this and they have made gonk changes to facilitate this stuff. See the discussion in https://github.com/apc-io/apc-firefox-os/issues/8. Are we talking to them? | ** Q: apc.io already is working on this and they have made gonk changes to facilitate this stuff. See the discussion in https://github.com/apc-io/apc-firefox-os/issues/8. Are we talking to them? | ||
*** A: [Tim] Thank you for bring this up. | |||
=== API addition === | === API addition === | ||