647237 - Iframe source leaks to other iframes

Status: UNCONFIRMED

(Core :: DOM: Navigation, defect)

Description

[Magnus]

User-Agent:       Mozilla/5.0 (Windows NT 6.0; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.0; rv:2.0) Gecko/20100101 Firefox/4.0

If you have several iframes on a web page, sometimes the source from one of the iframes also gets used on another iframe on the page. So if you have six iframes on a page displaying six different URLs, sometimes the iframes will display a URL that has been loaded into a iframe earlier on the webpage instead of the one given as a src.

Reproducible: Sometimes

Steps to Reproduce:
1. Clear the browser cache (ctrl+shift+delete -> cache)
2. Load the testcase on http://sitedirect.se/iframes/iframes.html ( download: http://sitedirect.se/iframes/iframes.rar) several times.

You might have to load the page 100 times (sometimes it displays an incorrect iframe on the first couple of page loads, but sometimes you have to reload the page for a couple of minutes before the errors are shown. It is somewhat random but it happens quite often.
Actual Results:  
Sometimes, the URL from a previously loaded iframe on the page leaks to a iframe further down on the page, displaying the contents loaded in (for example) iframe 1 on iframe 3 and 5

Expected Results:  
On every page load, the same frames should be loaded in the same order. All frames in the test have a text string followed by a number (1-5). On the sixth iframe, google.com should load.

The test case can be downloaded from
http://sitedirect.se/iframes/iframes.rar

Comment 1

[Magnus]

Attachment: Steps to reproduce test case in static HTML

The file contains six HTML files, one main page (iframes.html) which loads the other pages in iframes.

Comment 2

[Boris Zbarsky [:bzbarsky]]

How are you doing your reloads, exactly?  The exact steps; they matter.

Comment 3

[Magnus]

I use Ctrl + R to reload, but I have reproduced the error on the first page load (i.e. clear cache -> "Ctrl + L" + enter or by just typing the URL and enter) aswell.

I have also tried the following method to reproduce it
1) Load the page
2) If no error, reload it 20-30 times
3) If still no error, [Ctrl + shift + delete -> cache], Ctrl + L -> enter -> Ctrl + R (n times)

As a side note, when the error do occur, the next 1-3 page loads also contains the error, but usually the frames gets loaded in a different order then.

Comment 4

[Boris Zbarsky [:bzbarsky]]

OK.  Are you willing to try to find a regression range?  I realize it's difficult due to the unreliable nature of the problem....

Comment 5

[Magnus]

Sure. Any documentation about how I should do it?

But here is a few recollections from memory:
- The bug is only present in Firefox 4
- Every beta build I have tried has had the error (this is public betas). Cant recall which one was the first though, but I would guess it was 1-4 or so.

Comment 6

[Boris Zbarsky [:bzbarsky]]

> Any documentation about how I should do it?

https://github.com/harthur/mozregression is probably the simplest way to do this.

Comment 7

[Magnus]

I got this link from the command promt. 
http://hg.mozilla.org/mozilla-central/pushloghtml?starttdate=2010-08-20&enddate=2010-08-21
Also adding a list (as attachment) of dailys i manually tested in order to narrow the time span before running mozregression.

Comment 8

[Magnus]

Attachment: List of tested build outide of mozregression

Comment 9

[Magnus]

As a side note (based on my manual tests), it seems that the bug was introduced in beta 5 or very early in beta 6

Comment 10

[Boris Zbarsky [:bzbarsky]]

Olli, could this be fallout from bug 588643?  That would make sense if the right regression link is http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2010-08-20&enddate=2010-08-21