Re: [editing] Should the caret move by default, and should we define this behavior? (#58)

Yes, I was the one who suggested have those lists of use cases and goals.

But the fact contenteditable=true is broken doesn't mean that UAs need to have exactly one selection behavior and give up on platform friendless.  Gecko, for example, allows users to change the way selection behaves.  OS X has system-wide feature to enable split caret in bidirectional text.  All these things need to be respected, and I don't see exposing each and every one of those configurations to editors as an option because developers are bound to get some of them wrong.

We really need to understand exactly what's broken with selection and address those issues instead.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/58#issuecomment-108526971