Sorry wrong link. My comments actually apply what I said in 2 comments on GitHub at https://github.com/w3c/selection-api/issues/27#issuecomment-66353123
From: Olivier Forget [mailto:teleclimber@gmail.com]
Sent: Thursday, December 18, 2014 10:03 AM
To: Ben Peters
Cc: Frederico Knabben; Johannes Wilm; Ryosuke Niwa; public-editing-tf
Subject: Re: Default Caret and Selection Positioning Spec?
On Wed, Dec 17, 2014 at 3:02 PM, Ben Peters <Ben.Peters@microsoft.com<mailto:Ben.Peters@microsoft.com>> wrote:
> Ben, do your connections with the Office team mean we could find somebody
> knowledgeable to clue us in on what they feel is the "proper" behavior of
> the caret in a rich text editor and why?
I think 'proper' is important to consider, but personally I think 'predictable' is better for browsers. The input events spec [1] currently says that it should have 'left' gravity ('backward' coming soon) on click, and 'current side' gravity (if you're in an element, stay in it) on arrow keys, etc. This seems predictable to me and can be changed easily by script.
[1] http://w3c.github.io/editing-explainer/input-events.html#default-action-for-beforeinput
Ben, can you please clarify this? I don't see any of this terminology in the document you linked.
Received on Thursday, 18 December 2014 19:22:13 UTC