Firefox 17 doesn't support Greasemonkey

[Александр Omicron]

Hi! When Greasemonkey plugin will be updated to support new versions of FF?

[Anthony Lieuallen]

On Sat, Nov 24, 2012 at 11:34 AM, Александр Omicron <omicron.omicron...@gmail.com> wrote:

Hi! When Greasemonkey plugin will be updated to support new versions of FF?

https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/
"Works with Firefox 14.0 and later"

In what way does it not work?

[Omicron]

It is written in Firefox after latest update that this addon isn't compatible with this(17.0) version of Firefox and plugin now is turned off.

суббота, 24 ноября 2012 г., 22:17:16 UTC+2 пользователь Anthony Lieuallen написал:

[Trevor Jenkins]

On 25 Nov 2012, at 10:09, Omicron <omicron.omicron...@gmail.com> wrote:

> It is written in Firefox after latest update that this addon isn't compatible with this(17.0) version of Firefox and plugin now is turned off.

That's not a message I saw when I updated to FF 17.0 during this week and there's a smiling monkey face in my tool bar.

Regards, Trevor.

<>< Re: deemed!

[Omicron]

So, then what's the problem? FF sucks a little?)

воскресенье, 25 ноября 2012 г., 13:40:55 UTC+2 пользователь (Trevor Jenkins) написал:

[Trevor Jenkins]

On 25 Nov 2012, at 12:31, Omicron <omicron.omicron...@gmail.com> wrote:

воскресенье, 25 ноября 2012 г., 13:40:55 UTC+2 пользователь (Trevor Jenkins) написал:

On 25 Nov 2012, at 10:09, Omicron <omicron.omicron.omicron.omi...@gmail.com> wrote:

> It is written in Firefox after latest update that this addon isn't compatible with this(17.0) version of Firefox and plugin now is turned off.

That's not a message I saw when I updated to FF 17.0 during this week and there's a smiling monkey face in my tool bar.

So, then what's the problem? FF sucks a little?)

As the combination of FF and GM work for me I've no idea but other people have suggested that you check what version of GreaseMonkey you actually have installed. Fix that first then see whether FF still bitches at you.

Regards, Trevor.

<>< Re: deemed!

[Omicron]

Greasemonkey has the latest version. Updated it the day before the new version of FF is released.

воскресенье, 25 ноября 2012 г., 14:48:05 UTC+2 пользователь Richard написал:

On Sunday, 25 November 2012 10:09:12 UTC, Omicron wrote:

It is written in Firefox after latest update that this addon isn't compatible with this(17.0) version of Firefox and plugin now is turned off.

Double check that you have the current (1.5) version of Greasemonkey.

I had the same problem on upgrading to FF17, and discovered that something (maybe around the time of FF16) had stopped extensions updating.

In Addons I used the tools (gear button) to:

- Force all addons back to update automatically
- Force an update check now.

Turns out eight addons had fallen behind.

Richard

[Josef Davies-Coates]

Greasemonkey has completely stopped working for me too.

I'm on ubuntu 12.10 with firefox 17 and greasemonkey 1.5

[Josef Davies-Coates]

On Monday, 26 November 2012 11:12:02 UTC, Josef Davies-Coates wrote:

Greasemonkey has completely stopped working for me too.

I'm on ubuntu 12.10 with firefox 17 and greasemonkey 1.5

I'm not sure, but I think perhaps it was a very recent ubuntu update to firefox that broke it :-/

[Anthony Lieuallen]

On Mon, Nov 26, 2012 at 6:14 AM, Josef Davies-Coates <jo...@uniteddiversity.com> wrote:

I'm not sure, but I think perhaps it was a very recent ubuntu update to firefox that broke it :-/

Interesting.  I'm on Ubuntu (12.04) and the latest nightly of Greasemonkey without issue.  But I use stock Firefox from mozilla, not from Ubuntu's repositories.

Can anyone else confirm Ubuntu 12.10 and Ubuntu's latest Firefox + Greasemonkey 1.5 to be working or not?  (More quickly than I can build a VM to test that case with ...)

[James Wigley]

I'm using Ubuntu 12.10, Ubuntu's latest Firefox (17) + Greasemonkey 1.5 and it's not working.
The icon is shown on the addons toolbar, but scripts are not being executed.

[Anthony Lieuallen]

On Tue, Nov 27, 2012 at 8:50 PM, James Wigley <jwi...@gmail.com> wrote:

I'm using Ubuntu 12.10, Ubuntu's latest Firefox (17) + Greasemonkey 1.5 and it's not working.
The icon is shown on the addons toolbar, but scripts are not being executed.

Ok.  For users seeing this: If you download Firefox from mozilla.com does that binary exhibit the same broken behavior?

[James Wigley]

I just gave it a shot and the issue is still occurring for me.

I installed Firefox 17 from tar.bz2 to /opt/firefoxMoz, then ran it with firefox -no-remote -P "firefoxMoz".

[Omicron]

Firefox 17.0.1. The problem persists...

суббота, 24 ноября 2012 г., 18:34:03 UTC+2 пользователь Omicron написал:

[W]

Problem report. Greasemonkey is turned off until fixed

Operating System: Windows 7
Firefox version: 17.0.1
Greasemonkey version: 1.5

Exactly which script, if any, is causing a problem? - UNKNOWN

Exactly which page, if any, is exhibiting this problem.
USAJOBS.gov/Applicant/MyAccount/Home

This is my own personal account, and I am certainly not going to give the login and password.

The error is, that the ‘resume’ page tries to pull up a ‘view’ of my resume, with an option to ‘print’, but nothing comes up. This only happened after I installed a bunch of Firefox add-ons, so I painstakingly dropped them, one at a time, until I found out the problem only occurs when I have greasemonkey enabled. As soon as I disabled it – with all other add-ons active – the problem stopped.

The following extensions are installed and enabled in Firefox:
DownThemAll! 2.0.15
Flagfox 4.2.3
Greasemonkey 1.5
Local Load 1.0.6
Send to Kindle for Mozilla Firefox 1.02.54
WOT 20120926 (web of trust)

The following scripts are installed in greasemonkey:
Local Load Extended 0.2.2

[W]

Clarification: the firefox binary for the problem report I posted, was downloaded from the Mozilla website. everything else seems to work fine.

[Krisztián Tóbiás]

For me the GM_xmlhttpRequest absolutely don't work since the update (17.0.1)

GM_xmlhttpRequest({
  method: "GET",
  url: "http://users.atw.hu/pmpiac/json.php?name="..."&password="..."&id="...,
  onload: function (xhr) {
    var data;
    alert(xhr.responseText);
    try { data = JSON.parse(xhr.responseText);}
    catch(e) { data = eval("(" + xhr.responseText + ")");}...

the xhr doesn't get the data

[Scott Senften]

This has just started to happen to me as well. Greasemonkey has completely stopped work
Mac OS 10.7.5
Firefox 17.0.1
Greasemonkey 1.5

[Anthony Lieuallen]

On Wed, Dec 19, 2012 at 10:26 PM, Scott Senften <sen...@gmail.com> wrote:

This has just started to happen to me as well. Greasemonkey has completely stopped work
Mac OS 10.7.5
Firefox 17.0.1
Greasemonkey 1.5

I'd love to help you all, but it works for me.  There's a reason it doesn't work for you.  If I don't know what the reason is, I can't do anything.  So I need more information:
http://wiki.greasespot.net/Troubleshooting_%28Users%29
http://wiki.greasespot.net/Mailing_list#What_to_Say

[James Wigley]

Hi Anthony,
                After reading your latest response, I decided to have a closer look at the scripts I was testing with. It turns out, they were all were using CDATA to get around the annoyance of multi-line strings in javascript.
ie.

GM_addStyle((<><![CDATA[
.css {
   height: 32px;
}
]]></>).toString());

As E4X as been removed in Firefox 17, this no longer works. Using methods from the Greasespot Wiki work correctly though, so I updated the scripts and my issues are resolved.

So for me at least, it was actually script compatibility issues with changes in Firefox 17, not GM itself.

Thanks,

[Josef Davies-Coates]

I've realised that Greasemonkey IS actually still working with ubuntu 12.10, firefox 17.0.1 but these specific scripts have stopped working for me:

http://userscripts.org/scripts/show/95092

http://userscripts.org/scripts/show/126440

The latter is based on the former, so they are both almost identical scripts.

Both scripts still work with chromium using tampermonkey.

Anyone got any idea how I can get them working again with firefox?

Many thanks in advance,

Josef.

[Josef Davies-Coates]

Anyone got any idea about how I can get these scripts working in firefox again? (they still work in chromium)

Thanks!

Josef.

[LWChris@LyricWiki]

Hi Josef,

I used the Firefox error console (Ctrl+Shift+J) to get information about
the error. It says that "wrappedJSObject" is undefined. This is a good
hint on what is wrong with the scripts:

Greasemonkey has changed the way how scripts are executed on pages. When
scripts do not use the GM API functions, they aren't executed in the
protected sandbox anymore. As this script does not use API (which should
be stated by an "@grant none" keyword by the way) it is now executed on
the page itself, and thereby doing away with the sandbox pitfalls.
That "wrappedJSObject" was a way to bypass that security feature and get
the actual, unwrapped object behind/inside the so called XPC native
wrapper objects which GM scripts use when they are executed in the
sandbox. So the script should do away with that workaround stuff and
then explicitly state that it doesn't use any of the privileged GM APIs
and can be safely executed on the page.

Long story short: for the first script, delete the ".wrappedJSObject" in
lines 46 and 50. Then add "@grant none" to the header. It worked for me.
The second script will be pretty much the same, untested though.

Hope that helps,
Chris

[Anthony Lieuallen]

On Mon, Jan 14, 2013 at 4:34 PM, LWChris@LyricWiki <lwc...@gmx.de> wrote:

I used the Firefox error console (Ctrl+Shift+J) to get information about the error. It says that "wrappedJSObject" is undefined. This is a good hint on what is wrong with the scripts:

Good find!  Greasemonkey should perhaps detect this (usage of wrappedJSObject) and make it not fail.

[Josef Davies-Coates]

On Monday, 14 January 2013 21:34:02 UTC, LWChris wrote:

Long story short: for the first script, delete the ".wrappedJSObject" in
lines 46 and 50. Then add "@grant none" to the header. It worked for me.
The second script will be pretty much the same, untested though.

Thanks so much Chris, that worked! :)

(well, the new http://delicious.com seems to not work at all with greasemonkey enabled, so can't get that one working, but works for me on google links too :-D )

Here is the new, working, script that strips out Google's annoying re-direct links so that you can right-click copy link location from search results and then paste the link and not have the annoying google re-direct link:
http://userscripts.org/scripts/show/157189

Cheers,

Josef.

[Josef Davies-Coates]

On Monday, 21 January 2013 17:22:34 UTC, Josef Davies-Coates wrote:

On Monday, 14 January 2013 21:34:02 UTC, LWChris wrote:

Long story short: for the first script, delete the ".wrappedJSObject" in
lines 46 and 50. Then add "@grant none" to the header. It worked for me.
The second script will be pretty much the same, untested though.

Thanks so much Chris, that worked! :)

(well, the new http://delicious.com seems to not work at all with greasemonkey enabled, so can't get that one working, but works for me on google links too :-D )

Oh, it seems delicious does work with greasemonkey enabled, just not with my Delicious Redirect Link Cleaup script http://userscripts.org/scripts/show/126440 enabled.

Anyone got any tips on how to make it work again?