Peter Reporter
	Description • 20 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1

Assignments and comparisons using top.location are treated differently:

 - Making an assignment to top.location (eg. top.location = "www.mozilla.org")
navigates the topmost frame to that URL
 - Retrieving the property of top.location gives the URL displayed in the frame
named "top" [eg.  alert(top.location);   ]

Also seems to apply to window.top.location.

Reproducible: Always
Steps to Reproduce:
See testcase (should be posted immediately)
Actual Results:  
The message box keeps on displaying, requiring the user to hold down the ESC key
and wait until they get lucky

Expected Results:  
Regardless of how "top" is treated (whether it is always the Topmost Frame
Pointer or a pointer to the frame named "top"), assignment and retrieval of the
property should be treated the same!

Note: if "top.location" assignments become assignments to the frame "top" then
the testcase will result in an infinite loop of frames within frames within
frames (which will probably crash the browser?)

Bug will be fixed IF frames named "top" are made inaccessible by window.top (or
simply top)
Might be fixed by http://bugzilla.mozilla.org/show_bug.cgi?id=163924 (depending
on how it's fixed: nothing's happening with that bug, however)

	Brendan Eich [:brendan]
	Comment 2 • 20 years ago

DOM level 0, not JS engine -- reporter take note.

/be

	Gervase Markham [:gerv]
	Comment 3 • 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/

	Gervase Markham [:gerv]
	Comment 4 • 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.