[whatwg] classList should perhaps move from HTMLElement to Element
Jeff Schiller
codedread at gmail.com
Tue Nov 23 09:50:06 PST 2010
While we're on the topic of commonizing things at Element - can we introduce
an 'inner' property on Element? This would map to innerHTML for
HTMLElements. Other languages could introduce parsing rules for
getting/setting that property. Presumably XML grammars would use the rules
at http://dev.w3.org/html5/spec/apis-in-html-documents.html#innerhtml
Jeff
On Tue, Nov 23, 2010 at 9:20 AM, Anne van Kesteren <annevk at opera.com> wrote:
> On Fri, 19 Nov 2010 17:34:29 +0100, Boris Zbarsky <bzbarsky at mit.edu>
> wrote:
>
>> Given that SVG also has classes, it would make some sense to move
>> classList from HTMLElement to Element. That way SVG, and any other
>> languages that define classes (XUL comes to mind, actually) can benefit from
>> it as well.
>>
>> Note that Gecko's current classList implementation lives on Element.
>>
>
> My plan is to define Element.id, Element.className, Element.classList, and
> getElementsByClassName in DOM Core. And tie getElementById to Element.id
> somehow, tie Element.id to an attribute named "id", and Element.className to
> an attribute named "class".
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101123/76301477/attachment-0002.htm>
More information about the whatwg
mailing list