W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2014

Re: [whatwg] Move contentEditable/isContentEditable from HTMLElement to Element?

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 13 May 2014 16:21:05 +0000 (UTC)
To: Dirk Schulze <dschulze@adobe.com>
Message-ID: <alpine.DEB.2.00.1405131618230.27549@ps20323.dreamhostps.com>
Cc: whatwg <whatwg@lists.whatwg.org>
On Tue, 13 May 2014, Dirk Schulze wrote:
> 
> contentEditable can be fairly useful in SVG as well. It partly works for 
> inline SVG content in web browsers today.
> 
> The question is, should SVGElement add support for 
> contentEditable/isContentEditable and add it to its interface? Or should 
> both attributes move to the Element interface instead?

I would be very careful about moving global attributes to Element. Doing 
so implies that we are adding them to _all_ XML namespaces. That's a huge 
change to propose. Even with "class" it's IMHO going a bit far (we're 
saying that the semantics of <myvocab:teacher class="..."/> are that it's 
a space-separate list of CSS class names, even if the vocab designer 
intended it to be a room name or whatever).

I would feel more comfortable putting things on SVG, MathML, and HTML 
explicitly.

BTW, if anyone wants to move contenteditable="" to another spec, my 
suggestion would be that the place to move it to is the HTML Editing APIs 
spec, which could be renamed Web Editing APIs. There's precedent for 
having hooks for attributes like that, e.g. ARIA.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 13 May 2014 16:21:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:28 UTC