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

I think this ticket has covered several different issues that shouldn't have ben in the same ticket. I also think we are close to resolving, in which case we can close this ticket entirely.

All the initial things mentioned about RTL languages, delete to end of line, etc. seem to have been resolved.

As for the remaining issue:

As I understand it, this is about the two commands `deleteContentsForward` and `deleteContentsBackward`. These actually don't specify whether we are talking about graphemes, codepoints, tables, images, non-editable regions, or whatever.

Given that every code point seems to increase the length of a string y 1 in JavaScript, 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.

 > I think what@yosinch is saying is that browsers often have to do more intelligent things for Backspace to match to platforms behavior.

>From my eperimenting with the string above, 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. It is forward deletion that can be tricky, because the deletion of a base character also requires the deletion of all the associated codepoint 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/editing/issues/133#issuecomment-236479332