Comment #4 on issue 9883 by hb...@chromium.org: preventDefault on keydown from IME does not work http://code.google.com/p/chromium/issues/detail?id=9883
Thank you for your response. Yes, I know this sentence. On the other hand, I'm wondering about the semantics of "the respective textinput event" in the sentence. As far as I read this spec, this spec assumes every IME works as written in Appendix A.1.3. On the other hand, in fact, there are lots of IMEs which are not compliant with the Appendix A.1.3. At least on Windows, IMEs can send textinput events anytime they like to. We even realize that there are IMEs which don't send keydown events but send textinput events. This case happens when we use an IME which has its own window for input CJK characters and when we use mice (or tablets) to input CJK characters. So, I'm wondering how we can identify a textinput event as one created by a keydown event (or one created by another event, such as a mousedown event, etc.) when we use such IMEs not compliant with A.1.3. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
