465153 - Mouse icon is a stop symbol when tearing tab off the Firefox window

Status: RESOLVED DUPLICATE of bug 463088

(Firefox :: Tabbed Browser, defect)

Description

[Damian Shaw [Quan]]

Steps to reproduce:

1. Open a non-maximized Firefox window with multiple tabs
2. Click on and drag one of the tabs over the desktop
3. The mouse icon is a "stop" symbol

Expected results:

Something more intuitive than this.

Comment 1

[Matth78]

I notice that after trying to drag a tab over the deskbar it screws up tabs :

- the new blank window on close may report more than 1 tab opened. (I think to make it happens you have to got several tabs open in your "old" window)

- after closing the blank window, in your "old" one some tabs can't be closed anymore. (Especially the one you tried to tear off)

Comment 2

[Spencer Selander [greenknight]]

I also see the "stop" symbol. Plus, on XP, I tried, with 2 tabs open, dragging one to the taskbar; it opened a blank window, and closed the other tab. Definitely screwy.

 After that, I found that middle-click wouldn't open a link in a new tab. Left-click opened the link normally, but the back button wasn't highlighted.

Then I tried File -> Open New Tab - this opened a blank tab, and brought back the tab that had closed when I dragged the other tab. Seems to have restored normal function.

Comment 3

[Spencer Selander [greenknight]]

I was wrong about normal function, it's still screwed up. Tried to close this tab by clicking the X on the tab; no response. Right-click -> Close Tab didn't work, either.

Comment 4

[Bill Gianopoulos [:WG9s]]

(In reply to comment #1)
> I notice that after trying to drag a tab over the deskbar it screws up tabs :
> 
> - the new blank window on close may report more than 1 tab opened. (I think to
> make it happens you have to got several tabs open in your "old" window)
> 
> - after closing the blank window, in your "old" one some tabs can't be closed
> anymore. (Especially the one you tried to tear off)

One issue per bug.  Please file a separate bug on that issue.

Comment 5

[Bill Gianopoulos [:WG9s]]

Actually the Stop Icon issue might not be a problem.  The drag icon changes to a stop Icon at the point where it has already triggered the opening of the new window, at which point you should probably stop dragging.

Comment 6

[Bill Gianopoulos [:WG9s]]

(In reply to comment #5)
> Actually the Stop Icon issue might not be a problem.  The drag icon changes to

Strike that comment.

The way this is currently working is obviously not correct.

The only way to do the tear-off without getting the stop icon is to drag the tab to the content area.

Dragging the tab over any other part of browser chrome or outside the window results in the stop icon, yet releasing the mouse button at that point still results in the tear-off action.  Under no circumstances should any action be performed if you release the mouse button while a stop icon is displayed.

This issue does not occur under Linux, so I suspect it is Windows only.

Under Linux, dragging the tab over other parts of browser chrome or outside the window result in the tear-off but no stop icon.  So, it would seem that under Windows, it is the icon display that is incorrect.

Comment 7

[Bill Gianopoulos [:WG9s]]

I double checked the Linux action once more, and while I was correct in stating that dragging over other chrome elements does result in a the tear-off action, dragging outside the browser window does not.

Sorry for the bugspam.

Comment 8

[Matth78]

I just filled the bug 465167 - Dragging a tab outside the current window to tear it off in a new one screws up tabs.

Comment 9

[IU]

This bug is also preventing the ability to drag a link to a tab (to force it to open in that tab).

Comment 11

[Jim Mathies [:jimm]]

(In reply to comment #10)
> 
> *** This bug has been marked as a duplicate of bug 463088 ***

For issues specific to the cursor state, this was a known issue. Anything else should be files as a new bug.

Comment 12

[Damian Shaw [Quan]]

Thanks Jim for clarifying this :). I'll remove blocking bug as this is now a duplicate.