Greasemonkey 2.0+ fix(?)

General discussion, compatibility and contributed extensions.

Moderators: Lootyhoof, FranklinDM

Locked
User avatar
Lootyhoof
Themeist
Themeist
Posts: 1461
Joined: 2012-02-09, 23:35
Location: United Kingdom

Greasemonkey 2.0+ fix(?)

Post by Lootyhoof » 2015-03-06, 17:52

I've been looking into what's blocking Greasemonkey v2.0+ from working in PM. Turns out it's bug #952192 (to which Moonchild has answered previously).

WORKAROUND: 1. install.rdf version modification (to support PM25/FF24)
2. /modules/xmlhttprequester.js: REMOVE the following:

Code: Select all

this.sandboxPrincipal = Components.utils.getObjectPrincipal(sandbox);
This appears to disable Greasemonkey's built-in sandbox, which doesn't appear to exist in the last known working version (v1.15) anyway.

That's it, as far as I can tell. Everything else works perfectly. :)
Last edited by Lootyhoof on 2015-03-06, 20:33, edited 1 time in total.
Top
User avatar
New Tobin Paradigm
Knows the dark side
Knows the dark side
Posts: 8882
Joined: 2012-10-09, 19:37
Location: Skaro

Re: Greasemonkey 2.0+ fix(?)

Post by New Tobin Paradigm » 2015-03-06, 17:56

Thing is it would be nice if they would do a conditional to our appnsme/guid greasemonkey is to complex to fork
How far are you prepared to go? How much are you prepared to risk? How many people are you prepared to sacrifice for victory?
Are you willing to die friendless, alone, deserted by everyone? Because that's what may be required of you in the war that is to come.
Image
Top
Faust

Re: Greasemonkey 2.0+ fix(?)

Post by Faust » 2015-03-12, 04:46

Is there some way someone could post a copy of this modified extension? The sole reason I continue to use PM 24.7.2 is because of the Greasemonkey issue. I had hoped that this issue would have gotten fixed by now (yes, I know GM 1.15 supposedly works, but I tried in a recent PM portable and couldn't get any scripts to work).
Top
Tailszefox

Re: Greasemonkey 2.0+ fix(?)

Post by Tailszefox » 2015-03-12, 08:01

Posting modified XPI files is forbidden by the rules, as far as I know. For now we'll have to wait until PM implements the needed function. Changing the extension yourself to apply the fix is doable, but again, I think I've read that even giving instructions to do so is against the rules?
Top
User avatar
New Tobin Paradigm
Knows the dark side
Knows the dark side
Posts: 8882
Joined: 2012-10-09, 19:37
Location: Skaro

Re: Greasemonkey 2.0+ fix(?)

Post by New Tobin Paradigm » 2015-03-12, 08:06

I cannot take on a fork of greasemonkey. It is too complex. 1.15 IS fully operational with Pale Moon. I use it every day. We will however work with the developers of greasemonkey if at all possible but they need to come to us.
How far are you prepared to go? How much are you prepared to risk? How many people are you prepared to sacrifice for victory?
Are you willing to die friendless, alone, deserted by everyone? Because that's what may be required of you in the war that is to come.
Image
Top
Tailszefox

Re: Greasemonkey 2.0+ fix(?)

Post by Tailszefox » 2015-03-12, 08:08

I installed 1.15 and none of my scripts worked with it. To be fair, I migrated from Firefox 36, where I have the latest version of GM installed, so it's possible all my scripts are incompatible with older versions of GM, if only due to the slightly different syntax of the headers.

Either way, according to the comments on the pull request:
Just to update, I have requested for Pale Moon to add support for this function. I don't know any time-frame, but when it's done 9361136 should be unneeded.
So hopefully that won't be necessary soon.
Top
Locked

Return to “Browser extensions”