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

@BenjamP mentioned that co-editing scenario in the issue #18, and that makes me wonder maybe we should have a target range in device independent events.

Currently, we translate, say, a keyboard event `Ctrl+B` to a device independent event `Bold`, and it executes against the current selection. But if an editor wants to bold anywhere other than the current selection, the options are either to do it by own, or move the selection tentatively and move it back. The latter is likely to results in bad UX, and also could introduce weird bugs.

The proposal is, instead, `Ctrl+B` is translated to `Bold this range` with the targetRange set to the selection.

We can't then re-use `execCommand` or exiting code as is, but I assume we won't, so this change should not add a lot of work. Or is it only for Blink and WebKit?

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