Web sites should not be able to detect that Greasemonkey is installed

[janekptacijarabaci]

Ad http://www.mail-archive.com/greasemonkey-users@googlegroups.com/msg04550.html - nobody talks to me :-)

Is it really a mistake of Firefox? To me it looks like a bug in the Greasemonkey... Where is the truth?
If I'm wrong, close it...

But in this case:
What's the ticket (bugzilla) number, please? I still can not find it by search.

Can someone please answer my question?

[LouCypher]

Option 1 is Firefox's bug and has been fixed on Firefox 22
https://bugzilla.mozilla.org/show_bug.cgi?id=790732

Option 2 is likely Greasemonkey's.

[janekptacijarabaci]

Thank you.

Otherwise:
ScriptAddonFactoryByScript, ScriptAddonFactoryById, ScriptInstallFactoryByAddon, ScriptAddon, ScriptInstall...
This functions be used instead of GM_addonsStartup (or test all at once).
(all functions of this script - addons4.js)

Update:
resource://greasemonkey/GM_notification.js
typeof GM_notification

resource://greasemonkey/util/anonWrap.js
typeof anonWrap

etc.

To me it looks like a bug in the Greasemonkey...

• But I do not think so now

I reported to Bugzilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=903959

[jerone]

Option 1 seems fixed: http://jsbin.com/aWoGohe

Option 2 is negative: http://jsbin.com/aFihOFu

According to the bug report we need to replace every resource:// to chrome://.
Now the test is positive: http://jsbin.com/aFihOFu/2

[ArkadiuszMichalski]

Any plans to avoid using the second option? Now detecting GM is to easy.