Closed
Bug 65288
Opened 24 years ago
Closed 24 years ago
Dragging a link from one frame and dropping into another makes mozilla visit that link
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
People
(Reporter: xalkina, Assigned: bugs)
References
()
Details
I suppose it works with any page with two frames, but I have tested with Yahoo!
Mail. The above mentioned URL is not the actual page, you have to login to the
service.
This is what happens:
- Drag a link from left frame
- Drop the link to right frame
- Mozilla visits the link & displays it in its main window
I'm not sure whether this is considered expected behaviour, but doing the same
thing in a non-frame page does not have the same result.
I'm using linux/2001010921.
Have resubmitted this bug, but as I cannot find it in my queries, I'm sending it
again. Is there a problem with cookies @ bugzilla?
Comment 2•24 years ago
|
||
Confirmed
Platform: PC
OS: Linux 2.2.16
Mozilla Build: 2001011508
I am marking this NEW so someone higher up can decide if this is the correct
behavoir or not.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•24 years ago
|
||
Methinks this is an app-level GUI feature. ??? Trying to debug this, I get way
lost in .js and .xul files. So, I'm handing this bug to the module owner in
hopes that it will find it's way home. Please feel free to reassign as appropriate!
The fix for this bug should not change the behaviour of dragging a link from the
desktop to a frame - which should still target the toplevel content frame, as it
does in Nav 4.x. I've already heard several pleasantly surprised users comment
that we did this right.
Assignee: pollmann → ben
Component: HTMLFrames → XP Apps: GUI Features
QA Contact: petersen → sairuh
Comment 6•24 years ago
|
||
Actually, 4.x (on win32, at least) loads the url in the frame you drop it in.
*** This bug has been marked as a duplicate of 49722 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•