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

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

From: Ryosuke Niwa <rniwa@apple.com>
Date: Fri, 06 Jun 2014 09:55:18 -0700
Cc: Anne van Kesteren <annevk@annevk.nl>, Yoshifumi Inoue <yosin@chromium.org>, Robin Berjon <robin@w3.org>, Piotr KoszuliƄski <p.koszulinski@cksource.com>, Jonas Sicking <jonas@sicking.cc>, Ben Peters <Ben.Peters@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-id: <81E9624C-55BD-40F2-BC93-7E4A4D70F774@apple.com>
To: Julie Parent <jparent@gmail.com>
On May 29, 2014, at 3:50 PM, Julie Parent <jparent@gmail.com> wrote:

> Without default text input, the current proposal for contentEditable="minimal" is essentially just enabling cursors (drawing them, dispatching events, performing default actions).  Rather than calling the mode "minimal", which is ill-defined, why not explicitly call it what it is: "cursor-only"?  Or, have contentEditable take a list of features to turn enable: contentEditable="enable-cursors enable-CommandEvents".
> 
> Or, rather than tying this concept to contentEditable, with all the assumptions and complications that brings up, why not expose this building block as a completely separate attribute?

Explicitly listing features to enable sounds like a superior approach.

- R. Niwa
Received on Friday, 6 June 2014 16:55:48 UTC

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