Closed
Bug 207793
Opened 21 years ago
Closed 19 years ago
history.length in javascript is wildly wrong
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: alan, Assigned: radha)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4) Gecko/20030529
Start a new window and history.length is incremented from the parent window.
Back does not decrement the accessible value, although the browser back arrow
ghosts correctly.
The url given is one of two test pages that demonstrates this. Please let me
know if you cannot differentiate between the two.
Reproducible: Always
Steps to Reproduce:
1.In magpol.org for good reason in a new window I put :
if(history.length==0)window.close();history.back();
2.
3.
Actual Results:
Mozilla will never close the new window. IE works correctly.
Expected Results:
measured history.length correctly
Comment 1•21 years ago
|
||
new Windows -> history.length=1 - sounds logical to me...
Comment 2•21 years ago
|
||
---> History:Session
Assignee: rogerl → radha
Component: JavaScript Engine → History: Session
QA Contact: pschwartau → petersen
Comment 3•20 years ago
|
||
I've links like this one: <a href=".">Back</a> and I use JS to add
onclick="history.back()". If one opens page to new window/tab I cannot use
history.length==0 to force onclick assigment. I'm using this code to fix this
behaviour:
len = history.length;
if (navigator.product == 'Gecko')
len--;
If this would be fixed we will need code to distinguish between old and new
behaviour. Perhaps:
if (navigator.product == 'Gecko' && len!=0)
Comment 4•20 years ago
|
||
So what exactly is the bug here? Can someone attach a testcase showing the problem?
Comment 5•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 6•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Component: History: Session → Document Navigation
QA Contact: chrispetersen → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•