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

> Goals (https://w3c.github.io/editing/editing-explainer.html#goals):
>> 1. Empower authors with the right set of baseline behavior to enable creating complex editors
>> 2. Make it easy to implement custom behavior with appropriate APIs

Yes, those two goals is what at least I understand as "exposing primitives to JS". But lets just agree to disagree on this. 

> I understand your frustration but you really need to list concrete use cases instead of saying that you know it better.

Ok, what was not good enough about the use cases that were already listed?

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