W3C home > Mailing lists > Public > www-svg@w3.org > November 2010

Re: [whatwg] classList should perhaps move from HTMLElement to Element

From: Jeff Schiller <codedread@gmail.com>
Date: Tue, 23 Nov 2010 09:50:06 -0800
Message-ID: <AANLkTimNPuyBRoJg4tbORc82aj0FXJ67cC+6NLJ4P4KE@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: whatwg <whatwg@lists.whatwg.org>, Boris Zbarsky <bzbarsky@mit.edu>, www-svg <www-svg@w3.org>
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


On Tue, Nov 23, 2010 at 9:20 AM, Anne van Kesteren <annevk@opera.com> wrote:

> On Fri, 19 Nov 2010 17:34:29 +0100, Boris Zbarsky <bzbarsky@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/
Received on Tuesday, 23 November 2010 17:50:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:29 UTC