Re: [w3c/uievents] preventDefault() of keydown event should not kill composition start caused by the keydown (#180) from Masayuki Nakano on 2019-11-12 (public-webapps-github@w3.org from November 2019)

From: Masayuki Nakano <notifications@github.com>
Date: Mon, 11 Nov 2019 19:42:10 -0800
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/180/552720840@github.com>

Could be. However, there was a similar issue on Linux's GTK applications a decade or more ago (I don't know current status though). That is, the priority of IME key handling on GTK widget was lower than hot keys specified by application. That caused some IME users couldn't use IME on some applications. Then, IME started to use global key hook for wining GTK. So, I think that if web apps can do something for some key combinations which IME wants to use may reproduce such a11y issue on the web or IME starts to to hack something when browser has focus...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/180#issuecomment-552720840

Received on Tuesday, 12 November 2019 03:42:12 UTC