Closed Bug 201109 Opened 22 years ago Closed 19 years ago

Anchor links cannot always be dragged into new/existing window

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: chriseb, Assigned: jag+mozilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 If a link to another page which contains an anchor is dragged into another existing tab which is currently displaying a page, then nothing happens. Note that if the existing tab is blank, then the link is loaded up correctly. Reproducible: Always Steps to Reproduce: 1. Load up page in tab1, load up different page in tab2. 2. Drag link containing relative/anchor specifier from frame1 to tab2 Actual Results: Nothing Expected Results: tab2 should load up link.
->tabs
Assignee: asa → jaggernaut
Component: Browser-General → Tabbed Browser
QA Contact: asa → pmac
I've done a little more testing on this. Hence the change in the bug. What appears to be happening is this: When I drag a link that contains an anchor (i.e http://www.foo.com/some#anchor), the first time I can do one of a number of things with it including putting it into the blank area and having a new tab created and loading it up in an existing tab which may or may not be blank. However, after any operation like this the link appears highlighted, once this happens it is impossible to drag the same link and do any of the above. If the link is 'deselected' - by clicking elsewhere in the same frame, and then dragged again the operation will work.
Summary: Anchor links cannot be dragged into existing tab displaying other page → Anchor links cannot always be dragged into new/existing window
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.