Closed Bug 199471 Opened 21 years ago Closed 21 years ago

"Back" behavior totally hosed for iframes

Categories

(Core :: DOM: Navigation, defect)

Product:
Core
Component:
DOM: Navigation
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla1.4final

People

(Reporter: samh1974, Assigned: radha)

References

(
URL
)

Details

(Keywords: dataloss, fixed1.4, regression) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030326
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030326

It's impossible to navigate back/forward properly in IFRAMEs.  Even
right-clicking in the IFRAME and choosing "Back" will go back at the root
document level, not at the IFRAME level

Reproducible: Always

Steps to Reproduce:
1. Go to http://bugzilla.mozilla.org/
2. Go to report a bug
3. Search for a bug first. the results show up in the IFRAME
4. Either click "Back" on the browser toolbar or right click in the IFRAME and
click "Back"
Actual Results:  
The page went back to the list of areas to report bugs (browser, mail/news, etc)

Expected Results:  
The IFRAME contents should've gone back one, to the initial list of bugs.
same for me.
another page to test: http://normlife.host.sk/
click on a link in the display, try to go back: option greyed out.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030320 Phoenix/0.5

Yes same problem here, this is a serious bug IMO. This bug should have the
dataloss keyword.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030331 Phoenix/0.5
Flags: blocking1.4b?
Changed severity to 'major' and added 'dataloss' keyword
Severity: normal → major
Keywords: dataloss
Session history.

This works in 2003-03-05-10 and is broken in 2003-03-06-08.

The checkin that broke this is bug 148794.  See bug 14879 comment 21 for the
issues that apparently got ignored in the patch for that bug....
Assignee: asa → radha
Component: Browser-General → History: Session
Keywords: regression
OS: Windows 2000 → All
QA Contact: asa → petersen
Hardware: PC → All
changing severity to "critical" as an unsuspecting user could click "back" while
filling out a form or some other important function, and lose the data they've
entered.
Severity: major → critical
Flags: blocking1.4b? → blocking1.4b+
Flags: blocking1.4b-
Flags: blocking1.4b+
Flags: blocking1.4+
This should quickly get a dependency on bug #148794, and that one should
be reopened and blocking 1.4+. Tried it, but I cannot do that.

Because the decision in bug #148794 not to keep the track of iframe loads is
exactly what causes this problem here, so that one should be backed out.
Sounds like we are requesting just the opposite of that bug, but the fix there
was made with a work saving decision that caused this behaviour.
So the natural way would be to reopen that one and request a more complex fix
which incorporates the correct iframe behaviour.

Just my thoughts to keep the number of bugs and the spread of very closely related
problems over bugzilla small.
*** Bug 206555 has been marked as a duplicate of this bug. ***
The patch for bug 148794 has been backed out on the trunk (23 May) and the 1.4
branch (27 May). Closing this one and reopening that one.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.4final
Keywords: fixed1.4
*** Bug 208393 has been marked as a duplicate of this bug. ***
Verified on trunk and branch builds
2003-06-06-08 Mach0 and Win32 trunk
2003-06-06-05 Macho and 2003-06-06-04 Win32 branch.
Status: RESOLVED → VERIFIED
it still happens sometimes
right now i visitied Slashdot, then derstandard.at klicked on a Story, the back
and was again on slashdot.
Flags: blocking1.6?
ups... should have added my Version string before ;)

Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.5) Gecko/20031007 Firebird/0.7
What does that have to do with this bug?  There are no iframes on derstandard.at
that I can see...
my old bug concerning derstandard.at
(http://bugzilla.mozilla.org/show_bug.cgi?id=206555 ) has been marked a
duplicate of this bug, so i posted it here.
Ah, I see now. They create a whole mess of stuff with JS, including the iframe...
Please file a new bug on it, with a comment saying it's NOT this bug (since this
bug happened every time, so anything that's intermittent would not be this bug).
Flags: blocking1.6?
Component: History: Session → Document Navigation
QA Contact: chrispetersen → docshell
Hi! Guys it's totaly bad. I need you to fix it.
+1

This issue is still reproducible in firefox 54
You need to log in before you can comment on or make changes to this bug.