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

With access to the new contenteditable modes and the beforeInput/Edit event, one could instead have something such as model 3. Here only the changes in the JavaScript object version of the document need to be translated to DOM changes, not the other way round. This should -- at least in theory -- make it somewhat easier to create an editor that does not suffer from having to sync in both directions.
btw, the cEmode of the editable element in the DOM does not have to be cE=caret, but could also be a cE=typing, with all possible actions canceled by means of preventDefault. If we start out by only having cE=typing, this is probably what users will do.

Of course this is an incredible simplification of an editor that will be tens- to hundreds of thousands of lines of code, but for most of the basic editing operations, I think this should more or less capture it.
 
![model3](https://cloud.githubusercontent.com/assets/595512/9669587/72cafa92-5288-11e5-8c18-0f39287127fe.png)


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