Re: [w3c/selection-api] Specify Selection.modify()? (#37)

`modify` is useful, but awkward in that it just updates the selection, and provides no way to query a caret motion without messing with the active selection. I'm not opposed to specifying `modify` as it exists, but I think an interface that allows you to _query_ where a motion from a given position would go, without side effects, would be a lot more useful.

A further complication with that would be that selections, even cursor selections, contain additional hidden state beyond their parent node + offset (see #57, #32, probably there's more), and that kind of state needs to be accessible and representable to be able to properly model this.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/37#issuecomment-577741495