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

In WebKit, there are many caret movement behaviors that are platform specific.  While both Gecko and Trident/Edge tend to match Windows' caret behavior, WebKit tends to match OS X's.  So I don't really think we can agree on single caret behavior since that would cause a significant UX regression for many of our users.

Like I stated in another issue, the key here is to come up with a good abstraction to allow Web devs not to worry about platform-specific behaviors.  If anything, they can cancel the default action and implement their own caret behavior.

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