right mouse button stops working...

[SteC]

occasionally, i'll be browsing and suddenly my right mouse button stops working within the page area, no right mouse click menu and no mouse gestures. at that point, it still works fine in other windows (even other FF windows); it even works in the tab bar of the affected window, but not within the page.

unfortunately, i have NOT found a way to reproduce it on demand, so i can't narrow it down to any of the extensions i have installed.

i have no reason to believe that NoScript is causing or even contributing to this problem, but the only things that have changed recently, that i can recall, are:

• NoScript 2.0.3.2
• Ubuntu also pushed FF 3.6.10 a couple of days beforehand

i don't recall seeing this problem in the interim between these two, so since NoScript is the more recent update, i thought i'd start here.

has anyone seen any similar behavior? does anyone have any advice on what actions might precipitate such behavior? does anyone have any advice on how to diagnose and narrow the field of suspects when it does happen?

VERSIONS
Ubuntu Jaunty
FF 3.6.10
Adblock Plus 1.2.2
All-in-One Gestures 0.21.1
Clear Private Data... 0.2.3
Context Search 0.4.5
CS Lite 1.4
DownThemAll! 1.1.10
Extended Copy Menu 1.6.1
NoScript 2.0.3.2
Session Manager 0.6.8.3
Tab Mix Plus 0.3.8.4

[mander]

I have no idea what caused it, but I noticed the same thing this morning. For me none of the menus or status bar items worked either, but I could click on links and the buttons in the All-in-one Sidebar toolbar. I started by disabling Downloadthemall, which I had installed last night, and when I restarted Firefox everything worked. I re-enabled Downloadthemall and restarted, just to see what would happen, and everything then worked as expected again. Could it be that there is some kind of conflict between NoScript and Downloadthemall?

My reasoning is this: I found the original post here by googling for "Downloadthemall mouse not responding" or words to that effect. I notice that we both have both extensions, and when I tried disabling DTA everything started working again. I don't know what to do for a more comprehensive troubleshoot, though.

[SteC]

i'm sorry. i probably didn't make it clear: the problem is transient. when it happens, it only seems to affect the one window, and if you close that window and open another, the problem "goes away" (for want of a better term). so when you disabled DTA, you no doubt restarted FF, which would have "corrected" the problem.

i've noticed that occasionally i'll click the right mouse button to bring up the menu, but nothing will happen; clicking it again, usually brings up the menu.

also, i use mouse gestures frequently, and i have noticed that occasionally when i perform the gesture to close a window, it will close the window and then pop up the right click menu. i've also seen it where it will execute a gesture spontaneously, as if i'd released the right mouse button (but i hadn't).

this suggests that either something is actually generating the MouseUp event prematurely or FF is reporting and processing an event that didn't happen. under the circumstances, then, could this "phantom" mouse event be causing a problem with the MouseDown event handler for the right mouse button, either causing it to ignore events or disabling it entirely?

does any of this make any sense?

[therube]

If it were repeatable, on a particular page, it could just be the site using JavaScript to block right-click options.
(Not unheard of on picture sites.)

[SteC]

when it happens, it seems to affect all of the existing tabs in the given window as well as any new tabs opened in the same window. doesn't that tend to disprove the javascript theory? besides, javascript is disabled most of the time. i'll have to see if that tracks.

[Joao]

Confirmed to be NoScript. I installed NoScript in a semi-clean profile* and after signing in to Twitter right-click didn't work on a link.

I believe the site is random, however it did happen twice in a row on Twitter (both before and after I created the new profile).

Here is the error on the Error Console, which seems to appear after a "right-click timeout", i.e., not instantly (1 or 2 sec):

Error: Error: Cannot get outputNode by id
Source File: resource://gre/modules/HUDService.jsm
Line: 2276

* semi-clean profile = clean profile + places.sqlite, signons.sqlite, key3.db, sessionstore,js, sessionstore.bak from other session.

Versions:
----------
Firefox 4.0 Beta 6
NoScript 2.0.3.5
Kubuntu GNU/Linux 10.10

[Giorgio Maone]

@Joao:
your problem looks different that OP's.
Also, you're using a beta, so it might very well be a Firefox bug, which might be already fixed in a more recent build.
The error message is completely unrelated (it's about a console logging bug).
Could you check whether you can reproduce on latest trunk?

[Joao]

Ok, will test once the new Firefox beta is out.