Re: IsElement() and nsIElement

Boris Zbarsky <[email protected]> Fri, 23 Apr 2010 17:16:09 -0400
Newsgroups gmane.comp.mozilla.devel.dom
Message-ID <[email protected]>
On 4/23/10 3:55 AM, [email protected] wrote:
> I'm not a fan of the idea of spreading nsGenericElement around too
> widely, but if we rename it mozilla::dom::Element I'd be ok with that.
> But Ehsan does have a point in that it does contain a lot of internals
> that are never really meant for code outside of the guts of our
> elements, but those could of course be made protected etc. So I think
> if we pay attention to that and protect the internals, it could work,
> but writing a separate Element (or nsIElement) class would work for me
> as well.

OK.  I'm going to make an (empty for now) mozilla::dom::Element sitting 
between nsGenericElement and nsIContent.  Then we can hoist things to 
Element as desired, or wholesale rename nsGenericElement to 
mozilla::dom::Element at some point.

-Boris