- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 30 May 2014 08:25:08 +0200
- 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. -- http://annevankesteren.nl/
Received on Friday, 30 May 2014 06:25:59 UTC