Closed Bug 8955 Opened 25 years ago Closed 25 years ago

Frame menu links in new window open in old window

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: jay, Assigned: pollmann)

References

()

Details

(Whiteboard: [making test] csbooton@myna.com)

Attachments

(1 file)

If you open up a page with frames using File | New Browser Window...if you click on any links on the left frame (menu frame), the page opens in the old browser window (not the newly opened window). Here is an example: 1. Goto http://slip 2. File | New Browser Window 3. Goto http://slip in the newly opened window 4. Click on any of the links in the left frame The link you select should open in the right frame of the current new browser window, but it opens in the right frame of the old browser window. Machine: Win98 running build 1999062808
Summary: Frame menu links in new window open in old window → Frame menu links in new window open in old window
Whiteboard: [making test] csbooton@myna.com
I think that the target= property has not been implenented yet as as a result <a href> tags using a target= property will not work properly, try my site as http://members.xoom.com/CSBSkunk/pictures3.html , each thumbnail when clicked is meant to open in a new window, so you can view the pics and go onto the next one without having to press the back button. I attach a file from my site so you can see it for yourself.
Attached file the file from my site (deleted) —
Assignee: don → karnaze
Component: Browser-General → HTMLFrames
QA Contact: leger → beppe
Setting to correct component...beppe..a dup?
Assignee: karnaze → pollmann
Reassigning to Eric.
Severity: normal → major
Status: NEW → ASSIGNED
Target Milestone: M15 → M13
csbooton, I fixed the targetting bug a while back. I tried your attachment in today's apprunner build and it is working as you would like. To verify this, you may have to visit the URL as: bugzilla.mozilla.org/showattachment.cgi?attach_id=569 Because including the 'http://' in front caused the URL to be too long for me to visit. :S The other bug described by jpatel is something else. It is still present. I suspect it may be related to the fact that both of the apprunners have identical pages up, so there are two frames named "Display". The logic to determine whic frame to display in probably just uses the first one it comes to, which is the parent. If that is not it, it may be something more sinister, like event queues... I'm marking this M13, hopefully we'll get it fixed by then.
QA Contact: beppe → petersen
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I can not reproduce this bug. I am going to mark this bug worksforme even though I know somebody worked long and hard to fix it!
Status: RESOLVED → VERIFIED
Using the latest versuion (1999121508), I can't reproduce this problem either.
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: