Closed Bug 472685 Opened 16 years ago Closed 16 years ago

too easy to erroneously detach tab to a new window

Categories

(Firefox :: Tabbed Browser, defect)

3.5 Branch
All
Windows Server 2003
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 465184

People

(Reporter: arny.k, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2 (.NET CLR 3.5.30729)

New function in FF3.1 is obviously detaching tabs and moving them to another window when it is dragged away from the tab bar. I've observed how does it work and came to the conclusion that it simply does it when the area below the mouse cursor is not a valid target for tab move. However, it has a flaw: when trying to move a tab to itself it also constitutes invalid target and detaches the tab. The problem is, when I click on a tab, sometimes it happens I move a mouse before I release the button, so it becomes a grab instead of a click. The small movement results in dragging the tab to itself and it detaches and unintentionally moves to another window. It has happened several times to me, and you can expect it would happen many times from people not very skilled with mouse, not to mentioned physically impaired. Therefore, it should be prevented to happen when moving a tab to itself.

The other occasion this could happen is if someone begins moving the tab and changes his/her mind and simply returns tab to its original position - dragging it again to itself.

Reproducible: Always

Steps to Reproduce:
1. Grab a tab and start moving it
2. Stop moving the tab immediately, while mouse is stil over the tab
3. Release the tab
Actual Results:  
Tab detaches and moves to another window

Expected Results:  
Nothing
Flags: blocking-firefox3.1?
Version: unspecified → 3.1 Branch
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Flags: blocking-firefox3.1?
You need to log in before you can comment on or make changes to this bug.