- From: <bugzilla@jessica.w3.org>
- Date: Sat, 17 Mar 2012 06:46:26 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16329 --- Comment #2 from Masayuki Nakano <masayuki@d-toybox.com> 2012-03-17 06:46:24 UTC --- It's not canceling *launching* composition. The composition has been actually started and IE canceled the *started* composition. So, even if you cancel the composition, it cannot cause alternative keypress event for the pressed key. And this behavior can be only on some platforms which can discards the composition string. E.g., GTK doesn't have such APIs in its IM module. > However, it's very possible that I have some bad terminology in the spec. So, > without changing the cancelable nature of compositionstart, how would you > suggest this be better phrased? I think that spec should say "it depends on the platform or IME whether it's cancelable by calling preventDefault() of compositionstart." at least. However, I believe such difference between platforms must not be good thing for Web application developers because most of them must not familiar with every platform's APIs. Therefore, it *might* be better if it's impossible to cancel composition (only when it's caused IME) on all browsers. Or it might be better if there is an API in CompositionEvent for canceling the composition. E.g., "bool CompositionEvent.cancelComposition();". Then, we developers can see whether it succeeded or not. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 17 March 2012 06:46:28 UTC