RE: Only Text Input and Intention Events

This should either be in Selection API or a new related document. Could you please file bugs on Selection API and we can sort that out?

From: johanneswilm@gmail.com [mailto:johanneswilm@gmail.com] On Behalf Of Johannes Wilm
Sent: Thursday, December 4, 2014 11:24 AM
To: Ben Peters
Cc: Frederico Knabben; Olivier Forget; public-editing-tf
Subject: Re: Only Text Input and Intention Events

Hey,

On Thu, Dec 4, 2014 at 6:44 PM, Ben Peters <Ben.Peters@microsoft.com<mailto:Ben.Peters@microsoft.com>> wrote:
On Fri, Nov 28, 2014 at 1:03 AM, Frederico Knabben <f.knabben@cksource.com<mailto:f.knabben@cksource.com>> wrote:
> @Ben, btw, the proposed minimal cE includes caret movement and selection as
> well, right? In that case, please be sure to open a dedicated section in the
> spec just for that.

Selection should be handled in Selection API, and should work everywhere including cE=false, cE=typing, and cE=true. Is there anything special here that requires more logic for cE=typing?

It should be ensured that the movement of the caret is the same in all browsers. This is currently not covered by the Selection API, as far as I can tell, but maybe it would need to go there, as it applies to both cE=typing and cE=true.

There are some well-known issues with that now, mostly related to the caret "jumping" another character when moving across inline void elements, foreign elements (SVGs) or elements that are specified as being noneditable or the carent not being able to go certain places (such as before one of the before mentioned elements when these are at the start of a block element).  In all these cases, I believe it should be specified that these elements should be treated like single characters in relation to caret movement.



--
Johannes Wilm
Fidus Writer
http://www.fiduswriter.org<http://www.fiduswriter.org/>