Comment #6 on issue 9883 by jparent: preventDefault on keydown from IME does not work http://code.google.com/p/chromium/issues/detail?id=9883
Hmm, that language of "respective textinput event" is really confusing. I've noticed in Chrome, while using the standard Microsoft IME, I only get a textInput event after the IME accept functionality (this matches Appendix A.1.3). So, if I'm typing two latin characters to generate a non latin character, I get the sequence: keydown char1 keyup char1 keydown char2 keyup char2 keydown enter textInput keyup enter In this case, if I preventDefault() on the first keydown, I want it to not insert the character, which doesn't seem to have a corresponding textInput event (at least, not an event that the Javascript event system sees). There are two reasons Chrome's current behavior is problematic - 1. It functions differently than Safari 3/4 on Windows. This is a general compatibility issue. 2. It leads to bugs where applications work differently if the user is using an IME or not. For example, there are cases where an application wants to handle the keyDown themselves and not have the browser insert the character into the dom where it wants to, so preventDefault() needs to work, otherwise the application stops functioning as expected. -- 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 -~----------~----~----~----~------~----~------~--~---
