(Copied from my posting in the GM-users discussion group: http://groups.google.com/group/greasemonkey-users/browse_frm/thread/a6a9575e3329af84)
Every time I load a page, or switch tabs the following gets added to my
Error Console:
< GM_MenuCommander.attach
> GM_MenuCommander.attach
< GM_MenuCommander.detach
* this.menuPopup2: [object XULElement]
* this.menuPopup: [object XULElement]
> GM_MenuCommander.detach
This is beyond annoying as I'm trying to debug some other javascript
code at the moment.
Some responses with suggestions, and my responses, again from the aforementioned discussions thread:
On Nov 6, 10:16 pm, "Patrick Wiseman" <pwise...@gmail.com> wrote:
Disable all the GM scripts running on that page.
Patrick
It happens on every page, even with no scripts enabled, and with GM in
disabled mode.
On Nov 6, 10:53 pm, "Patrick Wiseman" <pwise...@gmail.com> wrote:
Apologies for asking, but you have cleared the Error Console?
GM_messages appearing when GM is disabled seems unlikely.
Patrick
Yes, I have cleared the Error Console after disabling Greasemonkey.
This is also how I identified that it's the exact the 6 messages
occuring each time I switch tabs or load a new page.
The messages all seem to come from internal GS calls to GM_log:
See:
http://greasemonkey.devjavu.com/browser/trunk/src/content/menucommander.js?rev=205#L93
http://greasemonkey.devjavu.com/browser/trunk/src/content/menucommander.js?rev=205#L111
http://greasemonkey.devjavu.com/browser/trunk/src/content/menucommander.js?rev=205#L98
On Nov 7, 4:00 am, BD <bdggetc...@donnelly-house.net> wrote:
Parts of Gm always execute, even when it is "disabled". Unless you use
the Firefox "disable this extension" feature, which requires a browser
reboot and might be a severe pain. I suggest you go into the code and
remove the offending error message code. It's pretty easy to do. You
should be able to find the code, but if you can't, I can suggest where
to look if you need me to remember where it is. (what is your OS?)
Of course, I could disable GM outright, and even uninstall it, but
then I'd loose all my GM scripts, which would be quite sad (having
written several myself, and even released a few of the more useful-to-
the-general-public ones: http://userscripts.org/users/627/scripts).
And yes, I could go into the extensions folder, extract the jar,
comment out the lines in menucommander.js. Of course, the next time
extension is updated, I'd have to repeat the whole process. This
doesn't really get to the root of the problem however, andI'd prefer
to see the issue tackled at the source (pardon the pun). I guess I'll
take this to the GM issue tracker.
On Nov 7, 9:46 am, Anthony Lieuallen <arant...@gmail.com> wrote:
It would appear, for some unknown reason, that you have the Greasemonkey
"logChrome" preference set to true. Open about:config and find the
"greasemonkey.logChrome" preference. If it's there and set to true,
that's why. Set it to false. If it's not, there must be a bug, somewhere.
Anthony,
The setting was not in about:config, and even after adding it manually
(as a boolean set to false), (even restarting firefox to be sure), the
problem persists. So indeed, there must be a bug "somewhere". :)
