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

Thanks for your comment, and confirmation of needing save/restore.

> I think the larger problem here is that the Selection API is a writable API, but there are internal states attached to Selections that aren't reflected in the API. How can this ever be problem free? If I have a writable API I am going to assume I can read and write to my heart's content. If there are hidden consequences to writing the API they should at the very least be documented, probably standardized, and ideally made writable too.

I think this is a separate issue. We're open source, we can expose what we keep as an internal state at a moment. But I'd like to discuss what to expose by what's needed, and what can be interoperable, not by what one implementation has. If exposing one of them can make editors better, I'd be very happy to discuss that. But I'm not positive to expose all what all browsers have internally.

Even if we exposed everything, save/restore is a separate story. You probably don't want to save 40 properties and restore, and it may be 41 tomorrow.

Save/restore can assure you to temporary change and restore selection without breaking anything including future, while we could discuss separately what other properties can make editors better.

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