W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: [editing] Leading with ContentEditable=Minimal

From: Julie Parent <jparent@google.com>
Date: Mon, 16 Jun 2014 17:12:39 -0700
Message-ID: <CAPSmAASnrbVLrz7H4W4qNZ_QF_pQ4vyFBaupq4QHAUW=YBhrnQ@mail.gmail.com>
To: Ben Peters <Ben.Peters@microsoft.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
If Intention events are (temporarily) moved out of scope, I think this
leads us back to the question of what would contentEditable='minimal' do
exactly?  Enable collapsed selections and default handling of cursor
movement ... anything else?  If this is all it would do, then perhaps what
we really want is an explicit API to enable cursors?


On Mon, Jun 16, 2014 at 11:12 AM, Ben Peters <Ben.Peters@microsoft.com>
wrote:

>  There’s been a good deal of discussion about the value of
> contentEditable=minimal. Some of us think that being able to cancel all
> browser actions with preventDefault on all Intention events is enough,
> while others believe that having a single way to stop browsers from taking
> action makes sense. I lean in the direction of the former, but there is
> another consideration- it will take more time to design and build Intention
> events in all cases, so why not work toward making contentEditable=minimal
> available, and then ship Intention events once we have a more complete
> story ready?
>
Received on Tuesday, 17 June 2014 00:13:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:25 UTC