Re: From Frozen to unfrozen state. hmm

George Johnstron <[email protected]> Mon, 1 Nov 2010 12:42:22 -0700 (PDT)

Newsgroups	gmane.comp.mozilla.devel.dom
Organization	http://groups.google.com
Message-ID	<ba477f28-4852-47fb-8762-b569958d15b3@r29g2000yqj.googlegroups.com>

On Sep 19, 7:26 pm, Boris Zbarsky <[email protected]> wrote:
> On 9/19/10 10:25 PM, Boris Zbarsky wrote:
>
> >> If you need to extent “nsIDOMHTMLImageElement” after it has been
> >> declared frozen why not implement “nsIDOMHTMLImageElement2” and
> >> inherit from “nsIDOMHTMLImageElement”?
>
> > Because that increases the complexity of the platform, slows down access
> > to both interfaces from JavaScript, and doesn't work for non-additive
> > changes.
>
> And to be clear, this particular interface isn't even one we control, so
> freezing it made no sense to start with.  It's the "HTMLImageElement"
> interface in the DOM 2 HTML or HTML5 specification.  It needs to change
> every time the latter changes.
>
> -Boris

And we can expect interfaces to remain unfrozen even during the RC
period?