- From: Johannes Wilm <notifications@github.com>
- Date: Sun, 31 Jul 2016 20:19:59 -0700
- To: w3c/editing <editing@noreply.github.com>
Received on Monday, 1 August 2016 03:20:29 UTC
I read through the spec draft, and actually it looks like it's already sayign what needs to be said: * deletion forward/backward doesn't say that it's only about graphemes * getTargetRanges should already provide information about what is to be deleted according to the logic of the given browser But I see that this may be something others may wonder about as well. I wonder therefore if we should: 1. Add the grapheme/codepoint thing on platform X as an example of what the targetRanges may return under specific circumstances. 2. More clearly list all the things that could be deleted after the two mentioned beforeinput events unless there is a non-collapsed selection (graphemes, codepoints, tables, non-editable areas, stub elements, etc.). This list may become very large though. --- 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-236480980
Received on Monday, 1 August 2016 03:20:29 UTC