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

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

From: David Bruant <bruant.d@gmail.com>
Date: Mon, 14 Jul 2014 15:07:06 +0200
Message-ID: <53C3D5FA.1010409@gmail.com>
To: Ian Hickson <ian@hixie.ch>, Dirk Schulze <dschulze@adobe.com>
Cc: whatwg <whatwg@lists.whatwg.org>
Le 13/05/2014 18:21, Ian Hickson a écrit :
> 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.
It might make sense to split the current HTMLElement interface and 
create a partial interface so it can be more easily reused in SVG and 
MathML.
Filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=26329 for that purpose.

David
Received on Monday, 14 July 2014 13:07:34 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:21 UTC