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

>Some of the beforeinput events require a target range that is different from the selection
How about adding `effectiveRange` to `beforeInput` to represent range will be removed?

>The `Range#expand()` that @foolip seems more meaningful, as it could be used to measure without losing the selection.

I disagree with `Range#expand()` but I agree to have`Selection#compute(StaticRange, alter, direction, unit)`
for purpose of UA's command, The API needs to work on *visible characters* rather than DOM characters.
I would like to keep `Range` to wok on DOM tree and isolated from *visible characters*.





-- 
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-292119174