Closed Bug 386276 Opened 18 years ago Closed 18 years ago

Clicking a link in an <iframe>/<frame> after going back doesn't do anything

Categories

(Core :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 364461

People

(Reporter: ispiked, Unassigned)

Details

(Keywords: regression)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070628 Minefield/3.0a6pre Steps to reproduce: 1. Go to http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox 2. Navigate around to other Tinderbox pages, go back to the Firefox page. Let the page automatically reload automatically, press the Go button to reload the page. 3. Click a link in one of the <iframe>s in the left sidebar; i.e. "SeaMonkey is closed, 6/28 17:28". Actual results: Nothing happens. Clicking the link doesn't take me to its destination. Expected results: I'm taken to the SeaMonkey tinderbox page. Note that step 2 sorta sucks. I'm really not sure how to get into the state where this happens, but it's also happened to me in Bonsai on pages such as this: http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=mozilla/embedding/config&command=DIFF_FRAMESET&file=basebrowser-mac-macho&rev1=1.57&rev2=1.58&root=/cvsroot in the frame there. Will try to get exact steps to reproduce.
Hrm, so I can reproduce this every time as follows: 1. Go to http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox. 2. Click the link in the SeaMonkey tinderbox <iframe> in the left sidebar ("SeaMonkey is closed, 6/28 17:49"). 3. (SeaMonkey tinderbox page should load.) 4. Press the Back button to go back to the Firefox tinderbox page. 5. Click the link in the SeaMonkey tinderbox <iframe> again.
Flags: blocking1.9?
Summary: Sometimes clicking a link in an <iframe>/<frame> doesn't do anything → Clicking a link in an <iframe>/<frame> after going back doesn't do anything
Yep. It does indeed. ;) This is basically bug 384977....
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.9?
You need to log in before you can comment on or make changes to this bug.