Re: [editing-explainer] Target range in device independent events (#39)

That's an interesting observation.

It seems to me that just adjusting the API isn't enough to ensure a bug-free editor for IME users. I am concerned that there are other things that might cause the UA to lose its internal state wrt IMEs. Perhaps DOM manipulations in the same region? 

Furthermore, even with a better API design there is no way to guarantee that devs are not playing loose with selections. Seeing as these internal states are completely hidden and silent, there is no way for an editor dev to even check if it's ok to touch anything. I think devs treat selections as something they can remember, change, and restore without consequence. And this is often needed when we want to let the user interact with another part of the UI or we need to do a DOM manipulation that might knock out the Selection.

I am not sure what the right solution is but it seems to me this should be taken into account in the IME discussion #34.



---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing-explainer/issues/39#issuecomment-69856574