W3C home > Mailing lists > Public > public-webapi@w3.org > August 2007

Re: Implementing HTMLDocument on all Documents (detailed review of the DOM)

From: Joćo Eiras <joao.eiras@gmail.com>
Date: Tue, 21 Aug 2007 16:23:47 +0100
Message-ID: <e72b1b360708210823k46a73952na5dfae0d9c095697@mail.gmail.com>
To: liorean <liorean@gmail.com>
Cc: "HTML WG" <public-html@w3.org>, "Web APIs WG (public)" <public-webapi@w3.org>
2007/8/21, liorean <liorean@gmail.com>:
>
>
> On 21/08/07, Simon Pieters <simonp@opera.com> wrote:
> > We'd rather have the members of HTMLDocument that are useful for all
> types
> > of documents to be moved to the Document interface. This would probably
> be:
> >
> >    * location
> >    * URL (also present in SVGDocument)
> >    * domain (also present in SVGDocument)
> >    * referrer (also present in SVGDocument)
> >    * cookie
> >    * lastModified
> >    * getElementsByClassName
> >    * innerHTML
> >    * activeElement
> >    * hasFocus
> >    * getSelection
>
> How about document.title?
>
> > Furthermore, it might make sense to move the following members from
> > HTMLElement to the Element interface:
> >
> >    * getElementsByClassName
>
> Does this make sense on Element? I mean, the class attribute and it's
> semantics are HTML/XHTML specific.


The same goes for innerHTML.
I agree there could be a generic property to access the markup directly, but
innerHTML's name is out of context.


--
> David "liorean" Andersson
>
>
Received on Tuesday, 21 August 2007 15:23:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:58 GMT