Re: [selection-api] caret-based selection movement (#27)

Here is what I'm hearing so far:
1) The location of the caret should be deterministic
2) For inline elements, it should be what we're calling "outside ~ inside", meaning it should have left-gravity, except for special cases.
3) BiDi behavior for arrow keys should not be spec'd because it's platform dependent.
4) We want to treat non-editable areas (ce=false, img, canvas, svg) as single characters.
5) We want to treat hidden elements as if they're not there at all. There is some concern about how to allow placing the caret on either side of such elements.

I agree with most of this. I think 3 doesn't really matter because we want to spec the default behavior of Responsive Input Events, not keyboard events. We should a good way indicate the platform agnostic meaning of the relevant beforeSelectionChange events, which is an open question I suppose.

I don't think 2 should have special cases. They can be handled in frameworks if they really matter.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/27#issuecomment-66353123