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

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

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 30 May 2014 08:25:08 +0200
Message-ID: <CADnb78i+6E95pEZ8QSzWHOcTX92y3mwa2-ST3GAUU3+HrW-Evw@mail.gmail.com>
To: Julie Parent <jparent@gmail.com>
Cc: 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>
On Fri, May 30, 2014 at 12:50 AM, Julie Parent <jparent@gmail.com> wrote:
> 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?

Just a DOM API perhaps as you're not going to get far without
scripting anyway? Interaction with contentEditable features will have
to be defined. This could maybe throw if the element was already
editable and if this is already active, maybe contentEditable stuff
should have no effect.

Received on Friday, 30 May 2014 06:25:59 UTC

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