Confirmed users
478
edits
User:Timdream/InputMethod API with hardware keyboard: Difference between revisions
Jump to navigation
Jump to search
m
User:Timdream/InputMethod API with hardware keyboard (view source)
Revision as of 07:23, 21 August 2013
, 21 August 2013→Idea
(Created page with "== Proposed API addition w/ hardware keyboard == ''This is not planned in Firefox OS v1.2.'' See [https://bugzilla.mozilla.org/show_bug.cgi?id=??? Bug ????]. === Idea === T...") |
m (→Idea) |
||
| Line 5: | Line 5: | ||
=== Idea === | === Idea === | ||
The previous iteration of IM API enables the keyboard apps to interact with the targeted input field. We would like it to handle the connected hardware keyboard as well. | The previous iteration of IM API (See [[WebAPI/KeboardIME]]) enables the keyboard apps to interact with the targeted input field. We would like it to handle the connected hardware keyboard as well. | ||
The API is designed to be compatible with previous iteration: if the hardware key is not <code>block()</code>'ed, Gecko would simply do it's usual things (sending the keydown/keypress/keyup events). If the keyboard app decide to <code>block()</code> the key, it would be responsible to come up with appropriate interaction, and do the desired mutation to the input field (if it decide to further swallow the original key events with <code>unblock(true);</code>. | The API is designed to be compatible with previous iteration: if the hardware key is not <code>block()</code>'ed, Gecko would simply do it's usual things (sending the keydown/keypress/keyup events). If the keyboard app decide to <code>block()</code> the key, it would be responsible to come up with appropriate interaction, and do the desired mutation to the input field (if it decide to further swallow the original key events with <code>unblock(true);</code>. | ||