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

> FYI: the testcase http://jsbin.com/wimuqowimu/15/edit?html,js,console,output won't work fine on Firefox 41 for Windows, unfortunately. Firefox 41 starts to support TSF on Windows. TSF is very rich framework, but very sensitive. For example, TSF doesn't allow to happen selection change/text change in focused editor at composition start. However, Firefox caches the previous contents of focused editor and lies TSF when it tries to query the content. If TSF-aware application returns unexpected content, TSF or some TIP (IME for TSF) may stop working :-( 

So it is currently working, but you are breaking it in the next version of Firefox? That does not sound like a step in the right direction. The spec says nothing about modifying the selection being forbidden as part of compositionstart, so that sounds as Firefox is planning to break with the spec?

> Anyway, I'll try to fix this bug latter...

Ok, so you agree that this is a bug and you will fix it?

 > If you said about http://jsbin.com/wimuqowimu/15/edit?html,js,console,output , this wants more hack for Firefox developers... I'm not sure if this can be fixed easy.

Not sure what you re saying here. This is the same example that you will be breaking in Firefox 41 on Windows, unless you fix it, that you mention above.

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