Re: [w3c/editing] Should we expose physical direction in Deletion commands? (for the case of RTL) (#133)

For an image, it is relatively unanbiguous. However, let's say the thing just before the caret is a table. Should the range contain the table? the last table cell? the last character in the last table cell? When moving away from exec command into JS driven things, this is precisely the kind of thing we want to leave up to JS.

If we include in the range whatever it is the browser would delete if it were the one doing the deletion and leave it at that, then JS has to go an analyze that, to see if it is a simple textual cases where it should follow the browser's advice by default, or if we're in a case where JS ought to make up its mind on its own. The risk is that naïve implementations may not think that there could be useful information about unicode characters in that range, and just always ignore it.

If instead we make it super easy to distinguish "this is just text deletion, and this range is one character worth of text", and "there's some markup in there, do your own thinking", we may increase the chance of naïve implementations getting text right.

---
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/editing/issues/133#issuecomment-236483862