- From: Klim Lee <notifications@github.com>
- Date: Wed, 24 Jun 2015 05:00:17 -0700
- To: w3c/editing <editing@noreply.github.com>
Received on Wednesday, 24 June 2015 12:00:44 UTC
> We should probably be more specific that these values come from CSS somehow. Yes, that’s what I mean. It’s just a matter of clear definitions. > If there strong will to extend the Selection API to also treat carets, then I am not strongly opposed to it. I’m not strongly opposed either, I just think we are more specific here than Selection should be; some of those concepts may map onto Selection pretty well, but some may not. Now, if everybody else see that differently, who am I to oppose? As long as it’s spec’ed somewhere, I’m fine. > This is more about the part of caret movement, right? It's not a problem if the caret can be programmatically placed anywhere inside a long series of white spaces, is it? I think so. The only problem is that on the caret between some 8 spaces, there will be spaces popping out of nowhere on input (as a result of de-collapsing). Not really the best experience. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/51#issuecomment-114844148
Received on Wednesday, 24 June 2015 12:00:44 UTC