Re: [uievents] specify how compositionend works if the caret has been moved to a different element (#5)

> Secondly, the spec reads "Event.target: focused element processing the composition".

It should be a bug of UI Events.

>  That is what Chrome/Safari do, while for Firefox the Event.target is the element that was focused BEFORE the composition started.

In these days, modern IMEs queries content information before compositionstart. Therefore, moving focus at compositionstart is too late for native IMEs.

Firefox guarantees that a set of composition events must be fired on an element. It should be better for web developers because compositionend events may not be fired if focus is lost from listening event target unexpectedly.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/5#issuecomment-137305943

Received on Thursday, 3 September 2015 02:42:44 UTC