576121 - imgIDecoderObserver methods visible as JS properties on img elements

Status: RESOLVED FIXED

(Core :: XPConnect, defect)

Description

[Bobby Holley (:bholley)]

I can reproduce this on both 3.6 and trunk with a clean profile (+firebug). This may be an issue with the way firebug is hooking in to things, or it may be a more real bug.

Steps to reproduce:
www.google.com
Activate firebug
Right click on google logo, inspect element
Activate the DOM tab on the right
Scroll down to the green+bold items

There are a number of methods of the form OnStop* and OnStop* which are imgIDecoderObserver methods:
http://mxr.mozilla.org/mozilla-central/source/modules/libpr0n/public/imgIDecoderObserver.idl

My understanding is that they shouldn't be there.

Comment 1

[Boris Zbarsky [:bzbarsky]]

They'll be there as soon as script somewhere QIs the image to imgIDecoderObserver...  Presumably Firebug is doing just that.

Comment 2

[Bobby Holley (:bholley)]

It also happens with the DOM inspector (and no firebug). I think the DOM inspector would be less likely to be QI-ing the image, no?

Comment 3

[Boris Zbarsky [:bzbarsky]]

Seems so, yes.  That just does a for/in loop, iirc....

Comment 4

[Blake Kaplan (:mrbkap) (inactive)]

I just tried this again and can't reproduce it. Bobby, can you still reproduce this?

Comment 5

[Bobby Holley (:bholley)]

(In reply to comment #4)
> I just tried this again and can't reproduce it. Bobby, can you still reproduce
> this?

I can reproduce it. I tested 2 configurations:

1-ff3.6, production firebug, clean profile
2-ff4b12, firebug 1.7a11, clean profile

I'm on OSX 10.6.

Comment 6

[Bobby Holley (:bholley)]

Taking. I'm working on xpconnect now, so I can scratch my own itch!

Comment 7

[Bobby Holley (:bholley)]

This is just going to go away with the new DOM bindings.

Comment 8

[Boris Zbarsky [:bzbarsky]]

This has been fixed ever since bug 825527 got fixed.  Also, imgIDecoderObserver is gone and imgINotificationObserver only has noscript methods.