InformAction Forums

Hello and Happy Holidays.

I use Firefox 9.0.1 with NoScript 2.2.4 on Mac OS X 10.6.8. In Console.app ClearClick events such as:
are logged when the Command-W shortcut is used to close a browser tab and go back to the previously active tab (even if the ClearClick warning setting is disabled, but as I understand it this is controlling the user pop-up message in Firefox itself). In this example the tab being closed was edition.cnn.com and the tab that became active was www.bbc.co.uk/news but it applies generally.

This does not happen when clicking File > Close Tab or when using the "x" tab close button. I haven't tried private browsing mode to see if it happens there but I will check that.

Is there some way to not have these logged to Console.app when Command-W is used?

Update: I tried private browsing mode and it can't be reproduced. After some more digging though I think the immediate solution is to set noscript.clearClick.rapidFireCheck to false in about:config. The implications of doing that I am not sure of yet.

Have you got any symptom beside the logged message?
If not, turning the preference back to true is advisable, since it protects against time-based clickjacking attacks.

Hi Giorgio

No other symptom no, it's just that I'd prefer these not to go to the OS X console. A visible warning in the browser would be ok I guess but I'm so used to using Command-W instead of other ways to close a tab and it's odd it's only that that causes the logging. I guess it's the difference between the keystroke and the mouse actions. Thanks for the information, I guess I have to weigh up the options.

Keep up the fantastic work on the #1 add-on for Firefox.

FWIW, I can't get a comparable error in Windows (XP, where the equivalent is Ctrl+Shift+W), so it's almost surely Mac-specific.
Thought: Since it's only on the keyboard shortcut, try changing the shortcut to something else, and see if it still happens?
Possible collision with another shortcut?

Update: I tried private browsing mode and it can't be reproduced

More leads, depending on how much time you want to devote to this. Does it work when both sites are allowed to set cookies? Both not?
History allowed, or not... you don't have to answer here; just offering some ways to isolate the trigger. The fact that it doesn't happen in Private Browsing is even odder than that it happens only on the keyboard and not on just closing the tab manually.

Agree that it seems harmless, but just some thoughts if you want to try to run it down.