Closed Bug 345687 Opened 18 years ago Closed 18 years ago

Frames appear empty or blank after returning to them, back or fwd

Categories

(Core :: DOM: Navigation, defect)

1.8 Branch
x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.8.1

People

(Reporter: tommyjb, Assigned: bryner)

References

Details

(Keywords: fixed1.8.1, regression)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060723 BonEcho/2.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060723 BonEcho/2.0b1

1. Visit any Google Images search-results page (e.g. <http://images.google.com/images?q=test>).
2. Click any of the result images.
3. Click 'See full-size image.' (at the top).
4. Click the browser's back button.

The two panes are now blank.  See attached screenshot.

Reproducible: Always
Attached image screenshot
OS: Windows XP → All
Version: unspecified → 2.0 Branch
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060723 Minefield/3.0a1
Not on trunk.
This regressed between 1.8.1b1_2006071708 and 1.8.1b1_2006071804 and this could point to Bug 314549.
https://bugzilla.mozilla.org/show_bug.cgi?id=314549#c27
Blocks: 314549
Status: UNCONFIRMED → NEW
Component: General → History: Session
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
QA Contact: general → history.session
Version: 2.0 Branch → 1.8 Branch
Flags: blocking1.8.1?
Another location where returning to frames pages draws blank frames: http://weilbacher.org/Mozilla/index.html
more apt description than "google images broken"
Summary: Google Images broken → content missing from frames pages returned to
Flags: blocking1.8.1? → blocking1.8.1+
*** Bug 346031 has been marked as a duplicate of this bug. ***
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1b1) Gecko/20060726 BonEcho/2.0b1

Same bug with:

1. Go on http://www.clubalpin.be/guides/topo/freyr/
2. Click on link "Les rochers"
3. Click on browser's back button

The frameset is displayed just blank.
Impossible to reproduce this bug bug with:

User-Agent: Mozilla 1.8b2 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050702
*** Bug 346580 has been marked as a duplicate of this bug. ***
Summary: content missing from frames pages returned to → Frames appear empty or blank after going back
Summary: Frames appear empty or blank after going back → Frames appear empty or blank after returning to them, back or fwd
Assignee: nobody → bryner
*** Bug 346677 has been marked as a duplicate of this bug. ***
WFM, Firefox 2.0b1 and SeaMonkey trunk on Linux.

To those that can reproduce the bug: does it occur in Safe Mode?
http://kb.mozillazine.org/Safe_mode
I can reproduce the bug in safe mode as well. But it appeared not in Fx 2.0b1 but in a nightly a couple of days later for me.
(In reply to comment #11)
>
Maybe you have bfcache disabled?
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1b1) Gecko/20060731 BonEcho/2.0b1

in safe-mode, I always reproduce it on:

http://www.clubalpin.be/guides/topo/freyr/
http://weilbacher.org/Mozilla/index.html

but not always on:

http://images.google.com/images?q=test

It depends on selected image and the related web site. But it's easy to find one that reproduce the bug.
For comment 4 SM has browser.sessionhistory.max_total_viewers set to 3.
Yeah, I had no luck reproducing with images.google.com, but the site in comment 7 reproduced this 100%.
Simple test case:  http://www.mscha.org/iframetest.html

Happens consistently there, for me.

 - Michael
Impossible to reproduce with trunk:

Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/2006080604 Minefield/3.0a1
Target Milestone: --- → mozilla1.8.1
I'm not able to reproduce this on a current Windows branch build, using images.google.com, http://www.mscha.org/iframetest.html, or http://www.clubalpin.be/guides/topo/freyr/, with max_total_viewers set to either 3 or the default of -1.
WFM in today's OS/2 SM branch
Yeah, almost certainly.
Status: NEW → RESOLVED
Closed: 18 years ago
Depends on: 347426
Resolution: --- → FIXED
Adding fixed1.8.1 keyword since comments (and a quick test on a branch build) seem to indicate this problem is resolved.
Keywords: fixed1.8.1
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: