[chromium-bugs] Issue 9883 in chromium: preventDefault on keydown from IME does not work

2009-04-10 Thread codesite-noreply
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

[chromium-bugs] Issue 9883 in chromium: preventDefault on keydown from IME does not work

2009-04-09 Thread codesite-noreply
Updates: Cc: o...@chromium.org Comment #5 on issue 9883 by jpar...@chromium.org: preventDefault on keydown from IME does not work http://code.google.com/p/chromium/issues/detail?id=9883 (No comment was entered for this change.) -- You received this message because you are listed in th

[chromium-bugs] Issue 9883 in chromium: preventDefault on keydown from IME does not work

2009-04-09 Thread codesite-noreply
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 e

[chromium-bugs] Issue 9883 in chromium: preventDefault on keydown from IME does not work

2009-04-09 Thread codesite-noreply
Updates: Labels: -Type-Bug Comment #2 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 bug report, and sorry for my slow response. Let me clarify your expected behavior befo