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

RE: [editing] Leading with ContentEditable=Minimal

From: Ben Peters <Ben.Peters@microsoft.com>
Date: Tue, 17 Jun 2014 00:56:12 +0000
To: Julie Parent <jparent@google.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <d2feae001f7c4e6cb95954043d6297d0@BLUPR03MB437.namprd03.prod.outlook.com>
On Mon, Jun 16, 2014 at 5:48 PM, Julie Parent <jparent@google.com> wrote:
>
> Yes. I really like the idea of explicitly enabling what you want and of
> separating the concepts.  Being able to turn on commandEvents independent of
> a cursor seems useful.  An API like this leaves far fewer questions of "what
> does it do?" than contentEditable="minimal".  What does cursor="true" do? It
> turns on the ability for the user or developer to place a cursor, and
> default movement.  It has nothing to do with dom modification.  What does
> commandEvents="true" do? It enables dispatching commandEvents.  No
> ambiguity.  However, this does make me think again about using
> beforeinput/input events rather than adding new CommandEvents, since those
> would include drag/drop and clipboard as well?

The way I see it is that <div>not editable at all</div> would get clipboard and drag/drop events, like it does today. <div commandEvents="true">build an editor here</div> would also get CommandEvents.
Received on Tuesday, 17 June 2014 00:56:53 UTC

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