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

You're extrapolating too much. I'm only concerned about real problems. I'm against any API unless it solves some problem is all I'm saying, and the list of problems each API solves needs to be explicitly documented. It's not enough to say "beacuse that's primitive necessary to build an editor". That's not a use case, and not any evidence to suggest the proposed API is necessary or the best appropriate form of the solution.

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