spatching of a compositionstart, compositionupdate,
or compositionend event.
I think this is wrong, if an IME is actively processing the input no
keypress event should fire.
]]
--
Masayuki Nakano
Manager, Internationalization, Mozilla Japan.
ancodes can be found in the Chromium source code
at:
http://code.google.com/searchframe#OAMlx_jo-ck/src/ui/base/keycodes/usb_keycode_map.h
That's interesting. But how should it behave with software keyboard on
mobile device?
--
Masayuki Nakano
Manager, Internationalization, Mozilla Japan.
ime:
4pm PDT (Tue) = 8am JST (Wed)
5pm PDT (Tue) = 9am JST (Wed)
--
Masayuki Nakano
Manager, Internationalization, Mozilla Japan.
depends on
the IME software one is using, and nothing guarantees browser
gets any sane key events.
-Olli
--
Masayuki Nakano
Manager, Internationalization, Mozilla Japan.
On 2016/01/12 14:02, Ryosuke Niwa wrote:
On Jan 11, 2016, at 8:26 PM, Masayuki Nakano wrote:
As far as I know, Gecko doesn't dispatch keydown nor keyup event for IME
unaware applications because JS changes something at keydown or keyup event
handler causes forcibly committing compos