There seems a conflict when we set contentEditable and designMode at the same time. Chrome browser has a similar problem on Linux.
Greetings, It seems this page changes the input focus while Editor::setComposition() sets the composition text. When moving the input focus, the FocusController class calls EditorClient::willSetInputMethodState() and EditorClient::setInputMethodState(). Unfortunately, several platforms (such as GTK, Win, and Chromium) finish the ongoing composition when the FocusController calls one of these functions. (Even though I have once added a workaround for this issue to Chromium, someone removed it somewhere between r50576 and r50677.) (*1) http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Win/50576/ (*2) http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Win/50677/ It may be a better idea to prevent the FocusController class from calling these functions while updating composition text rather than to add my old workaround to all platform code? (This issue happens on all platforms that implement either of the above functions as noted above.) Regards, Hironori Bono