Closed Bug 95801 Opened 24 years ago Closed 21 years ago

Frame loses its name after a page loads with javascript

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: mozilla, Unassigned)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.2) Gecko/20010707 BuildID: 2001062815 After loading a page into a frame that contains javascript code, the frame name either changes or is forgotten as subsequent directions at that frame cause a new window to open instead of going to the frame. Reproducible: Always Steps to Reproduce: 1. Load http://morons.org/news/ 2. Click on any of the first 8 links; none have javascript and all load up fine in the right frame 3. Click on "Alabama". It loads in the right frame and contains javascript. 4. Click on "Akron". A new window opens. Actual Results: New window opens containing the desired content rather than the right frame. Expected Results: Content displayed in right frame. This might be related to or the same as bug 70173. Turning javascript off alleviates the problem completely. Same results happen under both SunOS and Win2k.
[worksforme] in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4+) Gecko/20010927. Does not work in 9.4.
confirming on Win2k with build 2001100503.
The JS in question (in http://www.moreover.com/cgi-local/page?o=portal&feed=230) is: window.name = 'newsportal'; Over to DOM0 for now. jst, should setting window.name change the name that the URI targeter sees?
Assignee: pollmann → jst
Status: UNCONFIRMED → NEW
Component: HTMLFrames → DOM Level 0
Ever confirmed: true
OS: SunOS → All
Hardware: Sun → All
I would say yes, what does IE do?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.8
IE does exactly the same thing Mozilla does.
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Pushing out to mozilla1.1.
Target Milestone: mozilla0.9.9 → mozilla1.1
Target Milestone: mozilla1.1alpha → ---
Mass-reassigning bugs to dom_bugs@netscape.com
Assignee: jst → dom_bugs
Status: ASSIGNED → NEW
This is invalid. All browsers currently on the market interoperably handle the setting of window.name to mean that the name of the window as seen by "target" attributes is changed, which is exactly what we're doing.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.