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

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 
Filed for that purpose.


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