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

@kojiishi: How about this?
This first model is a basic sketch of how an editor handling IME could be structured as of today in browsers that can handle it (Chrome). The advantage is that one can keep changes below what is shown on the screen atomic and with that create a reasonably well-structured editor. But notice also that within the DOM representation of the document (red) there are arrows going both ways: so sometimes the JS needs to update the DOM because the document has changed or the IME in the Shadow DOM has finished creating some characters. This means one needs to introduce a more complex system of changing the DOM and monitoring user-originated changes to it, which is likely to end up being rather complex and possibly never quite perfect. 

![model1](https://cloud.githubusercontent.com/assets/595512/9669405/39176066-5287-11e5-9402-9a3eb3a232e6.png)


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