371246 - tab context menu remains after tab is closed

Status: NEW

(Firefox :: Tabbed Browser, defect)

Description

[paul stanton]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

a black box remains after a context menu is hidden as it's lost context from a closing tab.

or

context menu remains after it's tab is closed

see steps for more:

Reproducible: Always

Steps to Reproduce:
1. open multiple (2+) tabs
2. press but don't release the mouse scroll button on one of the tabs
3. right click the tab
4. release the mouse scroll button
Actual Results:  
a black box (menu drop shadow) sits over the page

or

context menu remains

Expected Results:  
menu properly removed and cleaned up.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070221 Minefield/3.0a3pre

In trunk I saw a toolbar-colored imprint instead of a black one but it took me 10 efforts.
Maybe in a way related to Bug 359418. Both lock up the context-menu in any case :).

Comment 2

[John]

It just closes for me.  However, this produces the effect:

1) Have two or more tabs open.
2) Right click (and hold) on one of the tabs.
3) Then middle click (and hold) on the same tab.
4) Then left go of the right mouse button.
5) Then let go of the middle mouse button (mouse wheel).

You should see a black box.

Comment 3

[Dave]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)

Bug happens as John describes it in Comment #2, except my box is gray.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

I'm not able to reproduce this problem with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) ID:2009021910

Can anyone run this test with a fresh profile and check if it happens too? Just to make sure no extension or pref settings are causing this issue.

Comment 6

[Dave]

I used a fresh profile, and the bug still occurs. I then started Firefox in safe mode using the fresh profile, and again it still occurs. This bug is not the result of add-ons or configuration.

To be clear, Paul Stanton's original procedure for this bug report does not cause the bug for me. However, John's procedure in Comment #2 does cause the bug every time. In case you missed it, here's the difference:
Paul: middle, right, middle, right.
John: right, middle, right, middle.