Open
Bug 188488
Opened 23 years ago
Updated 4 years ago
Forward session history removed by web page
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
NEW
People
(Reporter: mozilla, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030108
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030108
When I use the back button to go back to http://www.powergen.co.uk/ it is not
possible to use the forward button or display the forward session history,
although the buttons remain active.
Reproducible: Always
Steps to Reproduce:
1. Load http://www.powergen.co.uk/
2. Load another page
3. Hit the back button
Actual Results:
Browser goes back to http://www.powergen.co.uk/. The forward button and
dropdown remain active. Pressing the forward button or dropdown does nothing.
Expected Results:
Pressing the forward button should move forward one page in the session history.
Pressing the forward dropdown should display the forward session history list.
I originally found this problem when playing around with bug 185676, but I don't
think the two are related. I get the bug if I do the intellimouse "two pages
back" thing to the problem URL, but this bug occurs even on a clean browser run
when the intellimouse back/forward buttons are not used. FWIW, this works OK in
IE6.
Comment 1•23 years ago
|
||
This is the same here, but I think this is a problem of the webpage, the code
<body bgcolor="#FFFFFF" onLoad="resolution();">
runs javascript during loading the page and this script redirects to the real
page, thus removing the forward-history.
In my opinion, the browser cannot prevent this happening here...
| Reporter | ||
Comment 2•23 years ago
|
||
Yes, I see that now. Its not really a redirect, but a document.writeln. Is
there a standard describing how we should behave in this situation? Certainly
the situation can be handled as shown by IE6 (which maintains the entire history
despite the document.writeln), although this may be considered an enhancement or
might even be against a standard. What shouldn't happen is for the forward
button to remain active but not do anything. What do you think?
Comment 3•23 years ago
|
||
Yeah, we should either disable the button or (preferably) make it work.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
Updated•17 years ago
|
Assignee: radha → nobody
Updated•4 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•