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

>That's fine, but that's not what contentEditable=Typing set out to do. It's only about offering primitives to JS libraries to create editors. It is not about providing an editor to end users that works.

I beg your pardon?  I was right there when we initially came up with the idea of `contenteditable=typing` in the editing community group / WebApps, and I don't think "offering primitives to JS libraries to create editors" was really a goal in the first place or at least the way you described it here.  We had a specific list of [use cases](https://w3c.github.io/editing/editing-explainer.html#use-cases) we wanted to solve in contenteditable=typing as outlined in the explainer:

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

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