image onloads trigger more than amount of images on page




8 years ago
8 years ago


(Reporter: stewart.ridgway, Unassigned)


Firefox Tracking Flags

(Not tracked)





8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv: Gecko/20100625 Firefox/3.6.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv: Gecko/20100625 Firefox/3.6.6

If I have 10 images, each with an onload event that increments a counter, the counter equals (much) more than the amount of images on the page. 

It is working correctly in 3.6.3, IE8 and Chrome.

In the example I provided, the alert shows the current tally of loaded images on the left, versus total images on page.

In any other version or browser, the tally maxes out at the amount of images, as expected. In FF 3.6.6 it goes well beyond.

Reproducible: Always

Steps to Reproduce:
1. Go to Female models
2. Click on a model to view portfolio
3. Let the images load and take not of the alerted amounts
Actual Results:  
See details

Expected Results:  
See details
I can't reproduce your issue with Firefox 3.6.6, Firefox 4.0b1 and Seamonkey trunk on win32. I always get the correct image count.

Can you please try the Firefox safemode

Comment 2

8 years ago
Thanks! Disabling Add-Ons worked... 

Through process of elimination it seems that the Skype extension for Firefox is guilty. This is a widely used/common add-on, so will affect a lot of Firefox users. How can an add-on like that be able/allowed to interfere with a javascript result?

Should I submit the bug to them, or is this actually a bigger problem with Firefox security?
Every addon can format your hdd, send your private data including entered passwords to a remote server and it can do something like changing the image events. Addons can do the same that every windows application can do...
Mozilla can block specific addons but that is only done if the addons contains a security risk or causing crashes for every user.

Please report this to the skype extension authors.

PS: My own experience is that this is only a small issue compared with the other  problem that this addon caused in the past.
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.