Closed
Bug 272439
Opened 21 years ago
Closed 20 years ago
Links in separate window that target a specific frame causes new window to open
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: thomas.e.welch, Unassigned)
References
Details
Attachments
(1 file)
1.44 KB,
application/octet-stream
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041130
The following scenario used to work correctly in Mozilla 5.0 rv 1.7 (Firefox
0.9.2) When I upgraded Firefox to 1.0 (Mozilla 5.0 rv 1.7.5) the problem
started. This scenario also works correctly in IE 6.0.
I use a small navigation window to command a document in frame 2 of a 2 frame
frameset to scroll to a specific point. A link in the nav window looks like: <a
target="rightFrame" href=input.htm#one>One</a> The document in the frame has <a
name=one>, <a name=two>, etc. In the frameset, the frame 1 is named leftFrame
and the frame 2 is named rightFrame. When a link in the nav window is clicked,
instead of the doc in rightFrame scrolling to the correct location, a new window
opens containing the doc scrolled to the correct location.
Reproducible: Always
Steps to Reproduce:
1. Load document twoframe.htm
2. In frame 2, click 'Navigator'
3. In the Navigator Window, click any of the links
Actual Results:
Instead of the document in rightFrame scrolling to the requested location, a new
window opens with the document loaded and scrolled to the requested location.
Expected Results:
The document in rightFrame should have scrolled to the location specified by the
link in the navigator window.
Attachment #167441 -
Attachment mime type: text/html → application/octet-stream
![]() |
||
Comment 3•20 years ago
|
||
Actually, looks like the patch that went in in the end doesn't help here,
because of the document.write stuff... Bug 270414 covers that.
Depends on: 270414
![]() |
||
Comment 4•20 years ago
|
||
Fixed by checkin for bug 270414
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•