Re: [editing] ContentEditable with UserSelect=None needs to be documented (#20)

> * An editor that wants to place the caret in the same place when the user returns to a previously saved document.
> * A collaborative editor that wants to show the placement of the collaborators' carets.

These are good use cases.

>  * An editor that wants to implement movement in the block direction itself.

This is not.  This is _what_ an app wants to do.  A use case is _why_ it wants to do it.

> Sure, but in order to get it right, we should probably to continue to discuss based on the already given facts, and not restart the discussion from zero again.

That's just not how we design/standardize new APIs.  You're free to propose whatever you want but you won't persuade browser vendor to implement them with an argument like that.

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