Closed
Bug 207782
Opened 23 years ago
Closed 20 years ago
Implement Drag Link to same window
Categories
(Core :: DOM: UI Events & Focus Handling, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: tyl2, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030523 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030523 Mozilla Firebird/0.6
Currently it's not possible to easily drag a link to the active tab (this
includes the case where only one tab is open and the tab bar is hidden). One may
want to do this to avoid opening a new browser window when opening a link that
targets _NEW.
Reproducible: Always
Steps to Reproduce:
1. Drag a link but ensure that the mouse remains in the active tab window.
Actual Results:
The mouse icon changes to the Stop sign, indicating the action is invalid.
Expected Results:
The action is permitted. The page should load when the mouse button is released.
The current workaround is to drag the link to the Navigation bar and back.
Somehow the action is possible now.
=> Event Handling.
This seems to be a trivial thing to add, as there's already a 3kb "This Window" xpi.
Sorry for the bugspam. The xpi is just an alternative for opening links in the
current window, but I still think this is a UI bug where what you can do changes
depending on where your mouse has been.
Just to clarify, I'm not talking about dragging links to the tab bar. I'm talking
about dragging links to the current page, like dragging a link and dropping
it a few pixels off where it is. This should indicate to the browser you want
to load it in the same tab, but doesn't work until you have dragged it to the
navigation (back, forward, etc) bar first.
Comment 4•22 years ago
|
||
It is possible to work around:
Drag the link outside the page and back into. Now you can drop it!
Comment 5•22 years ago
|
||
the solution to this behavior is found in bug 207782
Comment 6•22 years ago
|
||
sorry the right bug# is 36867
Updated•22 years ago
|
Severity: minor → enhancement
Comment 7•20 years ago
|
||
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/
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•7 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•