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

> it seems that the targetranges can point specifically to either just a single unicode character which corresponds to a codepoint, or a series of characters which correspond to a base character and all its associated codepoints. If this is so, then it seems that this issue solves itself as long as we make sure that the targetranges point to what the browser believes should be deleted.

Makes sense to me. JS is free to ignore that information, but it's there in case it wants to follow browser/platform conventions.

> it seems that backspace actually is the easier operation, because one simply removes the last character without having to worry about what type it is

I think that depends on the language. Which brings us back to exposing what the browser would delete, and letting JS figure out if it wants to follow that or do something else.

One thing I am not sure about, is that if what's just before / just after the caret isn't just text (for example, an image, a table, a table cell border...) what do we put in the target ranges? Whatever structure the browser would act on if it were to do the forward/backward deletion, somehow (how?) stick to information about textual content only? No information if the thing immediately before / after the care isn't text?

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