Firefox 5 Breaking Greasemonkey? June 22, 2011 5:41 PM Subscribe
Firefox 5 breaking Mefi Greasemonkey Scripts?
I use the metafiltermultifavorites, Mefi Navigator, and Mefi Deleted post scripts (much thanks to the builders of them), but since I updated to Firefox 5, none of them are working (I checked that greasemonkey and the scripts are enabled).
Is anyone else having this trouble?
I use the metafiltermultifavorites, Mefi Navigator, and Mefi Deleted post scripts (much thanks to the builders of them), but since I updated to Firefox 5, none of them are working (I checked that greasemonkey and the scripts are enabled).
Is anyone else having this trouble?
Not to seem like I'm moderating the thread, but since it's pervasive across all the scripts (and by various authors), I thought I'd ask here to find out if other people were having the same problem.
It's not like the scripts are acting funny. They're not doing anything at all.
posted by chimaera at 5:59 PM on June 22, 2011
It's not like the scripts are acting funny. They're not doing anything at all.
posted by chimaera at 5:59 PM on June 22, 2011
How could they possibly have had time to add new broken things. Firefox 4 came out, like, 10 minutes ago.
posted by DU at 6:01 PM on June 22, 2011 [5 favorites]
posted by DU at 6:01 PM on June 22, 2011 [5 favorites]
ffx is now in a weird churnosphere. makes me sad.
posted by boo_radley at 6:06 PM on June 22, 2011
posted by boo_radley at 6:06 PM on June 22, 2011
Navigator seems to be working well for me. My favorite script, Metafilter Scroll Tag, though, not so much.
posted by Dumsnill at 6:07 PM on June 22, 2011
posted by Dumsnill at 6:07 PM on June 22, 2011
Yep, same here. Metafilter Multifavorited Multiwidth stopped working.
Seriously, Firefox, ending support for Firefox 4 three months after releasing it? Bad form.
posted by Paragon at 6:11 PM on June 22, 2011
Seriously, Firefox, ending support for Firefox 4 three months after releasing it? Bad form.
posted by Paragon at 6:11 PM on June 22, 2011
Srsly. I have add-ons that were updated for ffx4 that are listed as incompatible with ffx5. I mean really? It's not like I'm trying to shoehorn support into Netscape 8 or something.
posted by chimaera at 6:22 PM on June 22, 2011
posted by chimaera at 6:22 PM on June 22, 2011
Seriously, Firefox, ending support for Firefox 4 three months after releasing it? Bad form.
To be fair, FF4 was shit. It froze up on me every ten minutes. Good riddance.
posted by Sys Rq at 6:23 PM on June 22, 2011 [3 favorites]
To be fair, FF4 was shit. It froze up on me every ten minutes. Good riddance.
posted by Sys Rq at 6:23 PM on June 22, 2011 [3 favorites]
To be fair, FF4 was shit.
Worse than any experience I ever had with IE.
What happened to you, man? You used to be about the browsing.
posted by Trurl at 6:28 PM on June 22, 2011 [3 favorites]
Worse than any experience I ever had with IE.
What happened to you, man? You used to be about the browsing.
posted by Trurl at 6:28 PM on June 22, 2011 [3 favorites]
chimaera, when extensions stop working after an update it's usually not that big of a deal; most of the time you can use something like Nightly Tester Tools to force-ignore the alleged incompatibility and things will work fine. But with Greasemonkey, problems are typically caused by small changes to the way Firefox handles JavaScript, which trip up the userscript before it can properly execute. The only way to fix it in my experience is to alter the code so it plays nice with the new browser version. I just did something like this the other day; by comparing one of my favorite non-working scripts to a similar one that still worked on FF4, I discovered that I only needed to add a couple of variables to the old script to make it start working again. But that was only necessary because the author was incommunicado -- Plutor and other Mefi script authors will likely have their scripts repaired soon.
As for Firefox's release schedule, I heard they're focusing on more of a Google Chrome model of frequent minor tweaks rather than single huge overhauls very year or so. I just wish they wouldn't monkey with the code in such an intrusive way -- add-ons are so central to the user experience (Greasemonkey in particular), you'd think they'd be more careful about not rendering half of them inoperable with each minor revision. I stopped using Firefox entirely for a few months solely because some of my favorite extensions quit working.
posted by Rhaomi at 6:31 PM on June 22, 2011
As for Firefox's release schedule, I heard they're focusing on more of a Google Chrome model of frequent minor tweaks rather than single huge overhauls very year or so. I just wish they wouldn't monkey with the code in such an intrusive way -- add-ons are so central to the user experience (Greasemonkey in particular), you'd think they'd be more careful about not rendering half of them inoperable with each minor revision. I stopped using Firefox entirely for a few months solely because some of my favorite extensions quit working.
posted by Rhaomi at 6:31 PM on June 22, 2011
FFS, FF5!
posted by East Manitoba Regional Junior Kabaddi Champion '94 at 6:36 PM on June 22, 2011
posted by East Manitoba Regional Junior Kabaddi Champion '94 at 6:36 PM on June 22, 2011
Well, so far there's at least one other data point that someone with Mefi Navigator is working for them, but Metafilter Scroll Tag doesn't.
For me, Navigator doesn't work either, so I'm starting so suspect it's at least partly some sort of bad install on my end, but also partly FFx5 being rude and changing how it parses JavaScript.
posted by chimaera at 6:36 PM on June 22, 2011
For me, Navigator doesn't work either, so I'm starting so suspect it's at least partly some sort of bad install on my end, but also partly FFx5 being rude and changing how it parses JavaScript.
posted by chimaera at 6:36 PM on June 22, 2011
I'm running FF5 on Windows 7 and Mefi Navigator and Quote are working for me.
posted by octothorpe at 6:38 PM on June 22, 2011
posted by octothorpe at 6:38 PM on June 22, 2011
FFSSFSFSFF5 FFFS FF5FF5FF5FSSFSFSFF5 FFFS FF5FF5FF5FSSFSFSFF5 FFFS FF5FF5FF5FSSFSFSFF5 FFFS FF5FF5FF5
i cannot hear you over the static, please increase power to your antenna or relocate to higher ground.
posted by TwelveTwo at 6:43 PM on June 22, 2011
i cannot hear you over the static, please increase power to your antenna or relocate to higher ground.
posted by TwelveTwo at 6:43 PM on June 22, 2011
Actually, the scroll tag works fine now, too, it seems. Forget my comment.
posted by Dumsnill at 6:54 PM on June 22, 2011
posted by Dumsnill at 6:54 PM on June 22, 2011
Wait, there's a Firefox 5 now?
posted by box at 7:07 PM on June 22, 2011 [1 favorite]
posted by box at 7:07 PM on June 22, 2011 [1 favorite]
They grow up so fast these days...
posted by waterunderground at 7:09 PM on June 22, 2011
posted by waterunderground at 7:09 PM on June 22, 2011
I upgraded to FF5 today and both Mefi Navigator and Deleted Posts scripts are working for me.
posted by rsclark at 7:13 PM on June 22, 2011
posted by rsclark at 7:13 PM on June 22, 2011
There's a Firefox browser?!
posted by shakespeherian at 7:24 PM on June 22, 2011
posted by shakespeherian at 7:24 PM on June 22, 2011
Wait, there's a firefox 4 now?
oh god i am a failure
posted by elizardbits at 7:30 PM on June 22, 2011
oh god i am a failure
posted by elizardbits at 7:30 PM on June 22, 2011
FF5. Win 7. Deleted Posts and Comment Dividers are working fine. I'll check for Hide Obit Comments when the opportunity arises.
posted by vidur at 7:31 PM on June 22, 2011
posted by vidur at 7:31 PM on June 22, 2011
I play some browser-based games for which I have all manner of Greasemonkey scripts installed (haven't installed any Metafilter ones....yet) and am on the beta-tester release cycle, so I got FF5 a week or two ago, and absolutely panicked when I discovered that Greasemonkey didn't work, period. A couple fixes I found helpful (YMMV):
the Add-on Compatibility Reporter causes Firefox to assume all your add-ons are compatible so it will try to run them, even when it otherwise wouldn't, and also lets you report the broken stuff (whether that's more than a placebo I leave to you to judge). My problem was that beta FF5 just declared Greasemonkey incompatible and disabled it (and wouldn't let me re-enable it), even though everything basically still worked fine, and this fixed that easily enough. (You can also disable compatibility checking by mucking around in about:config, but I will leave that to you to google.)
Also a couple of my addons and scripts relied on there being a status bar down at the bottom, which Firefox got rid of for some odd reason, but there is an add-on that puts it back.
So I don't know if those will help with the specific problems you're having, but I figured I'd mention it on the off chance they might help somebody.
posted by mstokes650 at 7:35 PM on June 22, 2011
the Add-on Compatibility Reporter causes Firefox to assume all your add-ons are compatible so it will try to run them, even when it otherwise wouldn't, and also lets you report the broken stuff (whether that's more than a placebo I leave to you to judge). My problem was that beta FF5 just declared Greasemonkey incompatible and disabled it (and wouldn't let me re-enable it), even though everything basically still worked fine, and this fixed that easily enough. (You can also disable compatibility checking by mucking around in about:config, but I will leave that to you to google.)
Also a couple of my addons and scripts relied on there being a status bar down at the bottom, which Firefox got rid of for some odd reason, but there is an add-on that puts it back.
So I don't know if those will help with the specific problems you're having, but I figured I'd mention it on the off chance they might help somebody.
posted by mstokes650 at 7:35 PM on June 22, 2011
Navigator, scroll tag, and deleted posts scripts working fine for me on FF5, Windows7. Plus, I have a freaking permanent MeFi app tab! Best FF ever.
posted by donnagirl at 7:45 PM on June 22, 2011
posted by donnagirl at 7:45 PM on June 22, 2011
Speaking of FF5, anyone using it on a Mac yet? Before I upgraded, it said it would break the PDF reader extension. That also happened with FF4 and it was a total nightmare until some beautiful soul out there in the ether fixed it. But I don't want to go through that again.
posted by Conrad Cornelius o'Donald o'Dell at 8:06 PM on June 22, 2011
posted by Conrad Cornelius o'Donald o'Dell at 8:06 PM on June 22, 2011
So FF5 is the shit now? I used FF4 and decided to go back to FF3 and wait. FF5 is still beta right? On the page it looks like it's alpha.
posted by cashman at 8:06 PM on June 22, 2011
posted by cashman at 8:06 PM on June 22, 2011
FF5 is in regular release. On the main download page, it's the one you get. I can't say definitively that it's the shit, except for the app tabs, which now rule my life after an evening of use.
posted by donnagirl at 8:23 PM on June 22, 2011
posted by donnagirl at 8:23 PM on June 22, 2011
Using FF5 on newish iMac. No problems with Acrobat Reader 10.3.
posted by Lynsey at 8:57 PM on June 22, 2011
posted by Lynsey at 8:57 PM on June 22, 2011
So FF5 is the shit now? I used FF4 and decided to go back to FF3 and wait.
Curiosity piqued, I just downloaded it.
It seems to work. I'm going to try switching back. I've missed Add Bookmark Here like I can't tell you.
posted by Trurl at 9:24 PM on June 22, 2011
Curiosity piqued, I just downloaded it.
It seems to work. I'm going to try switching back. I've missed Add Bookmark Here like I can't tell you.
posted by Trurl at 9:24 PM on June 22, 2011
Ah. Mozilla seems to be devolving back to their pre-Firefox days. What a pity. They had a few great years, and it seemed like they were finally on the verge of driving the final stake through the heart of XPCOM and XUL.
Oh well. At least we've got WebKit. The unlikeliest of open-source projects, and weirdly one of the most successful.
posted by schmod at 9:27 PM on June 22, 2011
Oh well. At least we've got WebKit. The unlikeliest of open-source projects, and weirdly one of the most successful.
posted by schmod at 9:27 PM on June 22, 2011
FF5 in XP SP3 => Mefiquote and MeFi Navigator working fine.
posted by Chrysostom at 9:50 PM on June 22, 2011
posted by Chrysostom at 9:50 PM on June 22, 2011
Yeah now I have to recompile and patch their SDK every few months instead of years. Sigh.
posted by jeffamaphone at 10:20 PM on June 22, 2011
posted by jeffamaphone at 10:20 PM on June 22, 2011
This is what I am trying to tell all of you. The singularity is just going to be an infinite trouble shooting and debugging session. The speed of computers might be increasing exponentially, but so are the inconveniences. Sure, we might be gods, but we'll be so bogged down by compatibility issues it won't feel any different.
posted by TwelveTwo at 10:47 PM on June 22, 2011 [2 favorites]
posted by TwelveTwo at 10:47 PM on June 22, 2011 [2 favorites]
boo_radley: "ffx is now in a weird churnosphere. makes me sad."
What? Final Fantasy X is fine... it's sitting in my PS2...
Usually I'm among the first to hop on an upgrade. I've even done beta-testing. But I'm not upgrading to FF5 yet. Even though I know how to edit the extension files to fool Firefox into thinking an extension is compatible, I shouldn't have to. I *just* did it with FF4. Chrome is starting to tempt me.
posted by IndigoRain at 11:00 PM on June 22, 2011
What? Final Fantasy X is fine... it's sitting in my PS2...
Usually I'm among the first to hop on an upgrade. I've even done beta-testing. But I'm not upgrading to FF5 yet. Even though I know how to edit the extension files to fool Firefox into thinking an extension is compatible, I shouldn't have to. I *just* did it with FF4. Chrome is starting to tempt me.
posted by IndigoRain at 11:00 PM on June 22, 2011
FF5 on W7: Navigator works, Deleted doesn't.
posted by Alvy Ampersand at 11:01 PM on June 22, 2011
posted by Alvy Ampersand at 11:01 PM on June 22, 2011
Well thank you MetaTalk, I didn't know FF5 even existed. Just upgraded right then. Looks fast, i like it. Hopefully the ongoing problem with Sync is now resolved (my only issue with 4).
posted by wilful at 11:37 PM on June 22, 2011
posted by wilful at 11:37 PM on June 22, 2011
Anyone got Multifavorited Multiwidth working with FF5? It's the only one that broke for me, but I miss it already.
posted by Proofs and Refutations at 2:06 AM on June 23, 2011 [1 favorite]
posted by Proofs and Refutations at 2:06 AM on June 23, 2011 [1 favorite]
Forget Firefox 5 breaking Greasemonkey, usually new releases break damned near everything, from extension to themes, and I really hate it when I'm forced to use a shitty theme because hardly any are available.
Cutting edge isn't worth the hassle.
posted by bwg at 2:42 AM on June 23, 2011
Cutting edge isn't worth the hassle.
posted by bwg at 2:42 AM on June 23, 2011
For the first half of this thread I honestly thought that the people talking about something called "Navigator" were using Netscape Navigator to read MeFi.
posted by A Thousand Baited Hooks at 3:37 AM on June 23, 2011 [3 favorites]
posted by A Thousand Baited Hooks at 3:37 AM on June 23, 2011 [3 favorites]
Just downloaded FF5 now and Scroll Tag, Unicorn and Narwahl, and Deleted Posts are all working fine, along with Firebug. It still hitches when I try to quickly scroll down the page, just like FF4. In short, works exactly the same!
It may be time to go Chrome.
posted by slogger at 5:30 AM on June 23, 2011
It may be time to go Chrome.
posted by slogger at 5:30 AM on June 23, 2011
After 15 minutes of running FF5 it's acting like a buggy piece of shit...glitching, stalling, freezing, pinwheeling, crashing, needing a force quit. It's also been writing to disk constantly, sucking up all my CPU power. I don't think we can be friends.
posted by slogger at 5:47 AM on June 23, 2011 [1 favorite]
posted by slogger at 5:47 AM on June 23, 2011 [1 favorite]
Just so y'all know, Chrome supports Greasemonkey scripts natively - just click to install. You don't even need an add-on to run them.
posted by Happy Dave at 5:50 AM on June 23, 2011 [3 favorites]
posted by Happy Dave at 5:50 AM on June 23, 2011 [3 favorites]
Please don't begin sucking, Firefox. I've been virus free for years and years thanks to NoScript, and no such add-on exists for Chrome or IE.
posted by charred husk at 5:56 AM on June 23, 2011
posted by charred husk at 5:56 AM on June 23, 2011
Wait, FF4 was crap? I'm using it right now and it's awesome. Perfectly stable for weeks at a time (actually, it hasn't crashed a single time).
The only thing I don't like about Firefox in general, not 4 in particular exactly, is that they keep messing with the UI. AND making it harder and harder to make it actually usable. Open it up, stop clamping it down!
posted by DU at 5:57 AM on June 23, 2011
The only thing I don't like about Firefox in general, not 4 in particular exactly, is that they keep messing with the UI. AND making it harder and harder to make it actually usable. Open it up, stop clamping it down!
posted by DU at 5:57 AM on June 23, 2011
Paragon: "Seriously, Firefox, ending support for Firefox 4 three months after releasing it? Bad form."
I don't get this. No one complains that Google doesn't "support" Chrome 11, despite the fact it came out April 27. Firefox is just moving to small releases every quarter instead of big releases every year (or more). Chrome has been doing this for a long time to much applause, and now Firefox starts it and everyone complains (and considers moving to Chrome).
posted by Plutor at 6:03 AM on June 23, 2011
I don't get this. No one complains that Google doesn't "support" Chrome 11, despite the fact it came out April 27. Firefox is just moving to small releases every quarter instead of big releases every year (or more). Chrome has been doing this for a long time to much applause, and now Firefox starts it and everyone complains (and considers moving to Chrome).
posted by Plutor at 6:03 AM on June 23, 2011
chimaera: "I use the metafiltermultifavorites, Mefi Navigator, and Mefi Deleted post scripts (much thanks to the builders of them), but since I updated to Firefox 5, none of them are working (I checked that greasemonkey and the scripts are enabled)."
I'm using Firefox 5 (on Linux) and having no problems with Mefi Deleted Posts. Are you using the latest version of the script? Are you running the latest version of Greasemonkey (0.9.5)? Are any of your Greasemonkey scripts working?
posted by Plutor at 6:09 AM on June 23, 2011
I'm using Firefox 5 (on Linux) and having no problems with Mefi Deleted Posts. Are you using the latest version of the script? Are you running the latest version of Greasemonkey (0.9.5)? Are any of your Greasemonkey scripts working?
posted by Plutor at 6:09 AM on June 23, 2011
MeFi Scroll tag, Navigator, Deleted posts and GraphFi are all working for me in FF5, as well as the new GoodListenr room population script.
posted by taz at 6:22 AM on June 23, 2011
posted by taz at 6:22 AM on June 23, 2011
Chrome has been doing this for a long time to much applause from Chrome users, and now Firefox starts it and everyone who uses Firefox complains (and considers moving to Chromea more-stable fork).
I'm using Conkeror at home and completely loving it. I can't run it at work because of some proxy issue, but desperately wish I could.
posted by DU at 7:01 AM on June 23, 2011
I'm using Conkeror at home and completely loving it. I can't run it at work because of some proxy issue, but desperately wish I could.
posted by DU at 7:01 AM on June 23, 2011
Chrome updates invisibly, though. I have Firefox as a backup browser and yesterday couldn't pay the thing to update itself. I ended up having to just go to the Firefox download site and do a fresh install.
posted by shakespeherian at 7:26 AM on June 23, 2011
posted by shakespeherian at 7:26 AM on June 23, 2011
Yeah, that's the big difference. It's actually hard not to update to the latest Chrome. Whereas Firefox has always taken pains to not auto-update much, especially to major version (although I guess that may change now that they are planning on lots of major versions.)
posted by smackfu at 8:25 AM on June 23, 2011
posted by smackfu at 8:25 AM on June 23, 2011
Having run Chrome exlusively for a year now at home, I have to say I prefer the Chrome model. It's been extremely painless. I have found that not all greasemonkey scripts work on it though. Many are FF only (or were last time I checked).
posted by bonehead at 9:02 AM on June 23, 2011
posted by bonehead at 9:02 AM on June 23, 2011
I do like Chrome's model, although I'll admit it's weird having absolutely no idea what version of a piece of software I'm running, especially one that I use as heavily as my browser. Apparently I have version 12.something here at work (beta channel) although I had no clue until I looked just now. It's a very different experience and relationship to a program than I'm used to.
posted by shakespeherian at 9:07 AM on June 23, 2011
posted by shakespeherian at 9:07 AM on June 23, 2011
What bugged me most about FF, and one of the main drivers for switching for me was not the browser updates themselves, but the horribly intrusive procedure for add-on updates.
FF, in a sort of tragedy-of-nerdity, is extremely concerned that the user know exactly what's happeneing behind the scenes with add-on and plug-in updates. It makes you click on all kinds of dialogues to allow them to update, and then, usually requires a browsers restart. When all you want to do is qucikly go on-line and check something, having FF popup extra windows and dialogs to notify you that such-and-so REQUIRES an update NOW for URGENT SECURITY PATCHES, and takes a few minutes to do so, with multiple clicks to authorize everthing and at least one restart, well, it gets tiresome. Even with just a few add-ons, this got old fast.
(They did a similar thing with site security certs, which made using https to configure the home router really annoying. Who are FF to tell me that I can't trust my router?).
Chrome doesn't do any of that crap. I can tell it to keep current the few add-ons I do use and not bug me. Works great.
posted by bonehead at 9:18 AM on June 23, 2011
FF, in a sort of tragedy-of-nerdity, is extremely concerned that the user know exactly what's happeneing behind the scenes with add-on and plug-in updates. It makes you click on all kinds of dialogues to allow them to update, and then, usually requires a browsers restart. When all you want to do is qucikly go on-line and check something, having FF popup extra windows and dialogs to notify you that such-and-so REQUIRES an update NOW for URGENT SECURITY PATCHES, and takes a few minutes to do so, with multiple clicks to authorize everthing and at least one restart, well, it gets tiresome. Even with just a few add-ons, this got old fast.
(They did a similar thing with site security certs, which made using https to configure the home router really annoying. Who are FF to tell me that I can't trust my router?).
Chrome doesn't do any of that crap. I can tell it to keep current the few add-ons I do use and not bug me. Works great.
posted by bonehead at 9:18 AM on June 23, 2011
bonehead: "Chrome doesn't do any of that crap. I can tell it to keep current the few add-ons I do use and not bug me. Works great."
I think this is why I use Chrome to only browse trusted sites and FireFox to roam to new places. I love Chrome - it is fast and easy. But I don't trust it. I feel naked without NoScript and I'm not always sure what it is doing. And adding a plug-in? "This highly trusted colored tab extension will have access to all information on your computer and the color of your underwear. Is this okay?"
posted by charred husk at 9:25 AM on June 23, 2011
I think this is why I use Chrome to only browse trusted sites and FireFox to roam to new places. I love Chrome - it is fast and easy. But I don't trust it. I feel naked without NoScript and I'm not always sure what it is doing. And adding a plug-in? "This highly trusted colored tab extension will have access to all information on your computer and the color of your underwear. Is this okay?"
posted by charred husk at 9:25 AM on June 23, 2011
Chrome has a Noscript option built in.
posted by shakespeherian at 9:28 AM on June 23, 2011
posted by shakespeherian at 9:28 AM on June 23, 2011
Wndws 7 sp1, FF5.0. Scrpts r wrkng fn, bt thr sms t b sm srt f txt strngnss....
posted by Kronos_to_Earth at 10:26 AM on June 23, 2011
posted by Kronos_to_Earth at 10:26 AM on June 23, 2011
Happy Dave: "Just so y'all know, Chrome supports Greasemonkey scripts natively - just click to install. You don't even need an add-on to run them."
Do any of them work? That was one the main reasons that I finally gave up on Chrome last year as none of the greasemonkey scripts actually ever worked on it. Other reasons are Awesome Bar (dumb name but great functionality), you can't change the search engine on the fly and there's no tab list button.
posted by octothorpe at 10:41 AM on June 23, 2011
Do any of them work? That was one the main reasons that I finally gave up on Chrome last year as none of the greasemonkey scripts actually ever worked on it. Other reasons are Awesome Bar (dumb name but great functionality), you can't change the search engine on the fly and there's no tab list button.
posted by octothorpe at 10:41 AM on June 23, 2011
I have a fair number of scripts running in Chrome. Although not everything works, a good deal of them do.
posted by shakespeherian at 10:43 AM on June 23, 2011
posted by shakespeherian at 10:43 AM on June 23, 2011
After some considerable tinkering (uninstalling/reinstalling, making sure all my greasemonkey scripts are up to date), the tally is this:
Multi-width Favorited: still broke
Mefi Navigator: Works!
Deleted Posts: works!
So it looks like the right answer at this point is to talk to the script authors for individual failures. I still have no idea why greasemonkey as a whole didn't work at all until I had to go all scorched-earth on FF5, but it doesn't exactly endear me to the Mozilla team.
This is Javascript. It's a complete enough language that you can emulate linux in it, why does FF5 break previously functional scripts? Ugh.
posted by chimaera at 10:47 AM on June 23, 2011
Multi-width Favorited: still broke
Mefi Navigator: Works!
Deleted Posts: works!
So it looks like the right answer at this point is to talk to the script authors for individual failures. I still have no idea why greasemonkey as a whole didn't work at all until I had to go all scorched-earth on FF5, but it doesn't exactly endear me to the Mozilla team.
This is Javascript. It's a complete enough language that you can emulate linux in it, why does FF5 break previously functional scripts? Ugh.
posted by chimaera at 10:47 AM on June 23, 2011
Just would like to point out, for the record, that I'm not a fan of Chrome's half-assed Greasemonkey support. They ignore half of the APIs and make me jump through hoops to support them. For now, I have no interest in trying Chrome or Opera to any great extent for mostly that reason.
posted by Plutor at 11:36 AM on June 23, 2011 [1 favorite]
posted by Plutor at 11:36 AM on June 23, 2011 [1 favorite]
Firefox 5 breaking Mefi Greasemonkey Scripts?
I just wanted to point out that my Great-Grandfather would probably be unable to identify this as english.
posted by blue_beetle at 12:53 PM on June 23, 2011 [6 favorites]
I just wanted to point out that my Great-Grandfather would probably be unable to identify this as english.
posted by blue_beetle at 12:53 PM on June 23, 2011 [6 favorites]
Chrome does not render XML readably, which is reason enough for me to use both (and IE for certain stuff required at work-bleh).
posted by Chrysostom at 1:34 PM on June 23, 2011
posted by Chrysostom at 1:34 PM on June 23, 2011
Apparently I'm running Firefox 5 now - it didn't ask, it just happened. I've got my Mefi Scrolltag and quotes working, so I' won't complain.
posted by charred husk at 1:58 PM on June 23, 2011
posted by charred husk at 1:58 PM on June 23, 2011
I'm not upgrading the FF5 until it supports English (Australia). I'm much too poor a typist to do without my squiggly red lines.
posted by dg at 3:16 PM on June 23, 2011
posted by dg at 3:16 PM on June 23, 2011
...and I really hate it when I'm forced to use a shitty theme because hardly any are available.
Classic Compact works fine in FF5.
And Mozilla is playing a catch-up game with IE and Opera by jumping from 4.0 to 5.0 instead of 4.1, and up to 7.0 by the end of the year. Apparently people were seeing "Firefox 4" and "Internet Explorer 9" and deciding hey, nine is more than four so it must be better, which is why they're doing "major" releases instead of what would normally be a point release.
posted by Evilspork at 11:38 PM on June 23, 2011
Classic Compact works fine in FF5.
And Mozilla is playing a catch-up game with IE and Opera by jumping from 4.0 to 5.0 instead of 4.1, and up to 7.0 by the end of the year. Apparently people were seeing "Firefox 4" and "Internet Explorer 9" and deciding hey, nine is more than four so it must be better, which is why they're doing "major" releases instead of what would normally be a point release.
posted by Evilspork at 11:38 PM on June 23, 2011
Firefox updated to version 5 today, and yes, MetaFilterMultiFavorites is broken for me as well.
posted by marsha56 at 12:24 AM on June 24, 2011
posted by marsha56 at 12:24 AM on June 24, 2011
I recant everything I said about FF5. After a few restarts it's behaving much better. And all my Greasemonkey scripts are working.
posted by slogger at 6:16 AM on June 24, 2011
posted by slogger at 6:16 AM on June 24, 2011
Evilspork: "And Mozilla is playing a catch-up game"
Dear god, I'm glad I don't work for MoFo. The shit they're getting for trying to Release Early And Often is amazing.
posted by Plutor at 6:21 AM on June 24, 2011
Dear god, I'm glad I don't work for MoFo. The shit they're getting for trying to Release Early And Often is amazing.
posted by Plutor at 6:21 AM on June 24, 2011
> The shit they're getting for trying to Release Early And Often is amazing.
FF's popularity is heavily dependent on its plugins. Without plugins, it's Joe Shmoe in his underwear.
If its default behavior in a lot of areas couldn't be fixed with plugins, I wouldn't use it. Every time a new FF version comes out and installs itself I have to check and see which plugins it disabled and search for a compatible version (no, it doesn't always find these automatically even when they exist); or if there really isn't one, then go in and edit the previous plugin installer file to lie about what FF version it's compatible with and hope for the best; or if neither of these works, then go search for a sort-of-work-alike plugin.
So far I've been willing to tolerate this--while major releases were rare. If they're going to happen every couple of weeks then I'm looking for a different browser with better stability. And if I were a plugin writer I'd say fukit and go do something else.
The amount of talking and bragging the Mozilla folks have done over the years about FF's wondrous customizability via plugins, you'ld would think they would understand by now that the plugins are their browser's clothes. Most of us look pretty silly if we forget to dress before we go out.
posted by jfuller at 8:03 AM on June 24, 2011 [1 favorite]
FF's popularity is heavily dependent on its plugins. Without plugins, it's Joe Shmoe in his underwear.
If its default behavior in a lot of areas couldn't be fixed with plugins, I wouldn't use it. Every time a new FF version comes out and installs itself I have to check and see which plugins it disabled and search for a compatible version (no, it doesn't always find these automatically even when they exist); or if there really isn't one, then go in and edit the previous plugin installer file to lie about what FF version it's compatible with and hope for the best; or if neither of these works, then go search for a sort-of-work-alike plugin.
So far I've been willing to tolerate this--while major releases were rare. If they're going to happen every couple of weeks then I'm looking for a different browser with better stability. And if I were a plugin writer I'd say fukit and go do something else.
The amount of talking and bragging the Mozilla folks have done over the years about FF's wondrous customizability via plugins, you'ld would think they would understand by now that the plugins are their browser's clothes. Most of us look pretty silly if we forget to dress before we go out.
posted by jfuller at 8:03 AM on June 24, 2011 [1 favorite]
bonehead: "What bugged me most about FF, and one of the main drivers for switching for me was not the browser updates themselves, but the horribly intrusive procedure for add-on updates."
4 as had an integrated add-on tab for a while now. Updates are silent. Last version with a pop-up add-on updater was 3. Last add-on update I got was yesterday, and I had to manually tell it to show me recently updated add-ons to even know this.
Have been running the 5 beta for a while now, didn't know 5 officially dropped. I like it a lot. On a Mac it's smoother than 3 ever was.
posted by caution live frogs at 10:27 AM on June 24, 2011
4 as had an integrated add-on tab for a while now. Updates are silent. Last version with a pop-up add-on updater was 3. Last add-on update I got was yesterday, and I had to manually tell it to show me recently updated add-ons to even know this.
Have been running the 5 beta for a while now, didn't know 5 officially dropped. I like it a lot. On a Mac it's smoother than 3 ever was.
posted by caution live frogs at 10:27 AM on June 24, 2011
> Updates are silent.
If there is an update, and FF can find it. If not, disabling the add-on without so much as a by-your-leave is silent too. That's intrusive.
I'm looking for the configuration option where you tell FF "Don't disable my add-on even if the install.rdf says maxVersion is 3.5. If it breaks the browser that's my concern, not yours." Haven't found it yet.
posted by jfuller at 10:40 AM on June 24, 2011
If there is an update, and FF can find it. If not, disabling the add-on without so much as a by-your-leave is silent too. That's intrusive.
I'm looking for the configuration option where you tell FF "Don't disable my add-on even if the install.rdf says maxVersion is 3.5. If it breaks the browser that's my concern, not yours." Haven't found it yet.
posted by jfuller at 10:40 AM on June 24, 2011
jfuller, you can get that behavior if you install the Add-on Compatibility Reporter.
By the way, I do work for Mozilla and apologize for any teething problems from our new release process. We're doing everything we can to keep it from being disruptive, like updating add-ons automatically to be compatible with new versions. But the first couple of releases will probably hit some snags that we didn't forsee or weren't able to fix in time.
By the way, we are not doing this to play "catch-up" in version numbers. Average users don't even know what versions of software they are using, so why would be bother? (The official announcement of Firefox 5 did not even mention the version number, and Google doesn't mention Chrome version numbers in their announcements either.)
posted by mbrubeck at 12:11 PM on June 24, 2011 [2 favorites]
By the way, I do work for Mozilla and apologize for any teething problems from our new release process. We're doing everything we can to keep it from being disruptive, like updating add-ons automatically to be compatible with new versions. But the first couple of releases will probably hit some snags that we didn't forsee or weren't able to fix in time.
By the way, we are not doing this to play "catch-up" in version numbers. Average users don't even know what versions of software they are using, so why would be bother? (The official announcement of Firefox 5 did not even mention the version number, and Google doesn't mention Chrome version numbers in their announcements either.)
posted by mbrubeck at 12:11 PM on June 24, 2011 [2 favorites]
FF5 & Mac
Mefiquote: works
Navigator: works
Thread Highlights: works
Scroll Tag: works
Howls Of Outrage: works
Usernotes: does not work
Multifavorited: does not work
posted by danny the boy at 2:03 PM on June 24, 2011
Mefiquote: works
Navigator: works
Thread Highlights: works
Scroll Tag: works
Howls Of Outrage: works
Usernotes: does not work
Multifavorited: does not work
posted by danny the boy at 2:03 PM on June 24, 2011
Hey, thank you very much, mbrubeck! I'll certainly give that a through-the-wringer.
Very much needed right now, too, I see. I just happened to look at your mefi profile at a moment when your latest tweet was "Firefox 6 Beta which will be released in about a week" -- and the Add-on Compatibility Reporter page you linked to mentions that it's already been checked in FF 7.0a1. Looks like FF releases really will be coming thick and fast.
N.b a comment from nutellajunkie on the Compatibility Reporter d/l page notes that there's an about:config tweak to do the same thing. Didn't say what it was but the bare mention made me curious enough to go digging. I found a very clear explanation of disabling the compatibility check with about:config here in Mozillazine.
Thanks again, fuller tips hat!
posted by jfuller at 3:53 PM on June 24, 2011
Very much needed right now, too, I see. I just happened to look at your mefi profile at a moment when your latest tweet was "Firefox 6 Beta which will be released in about a week" -- and the Add-on Compatibility Reporter page you linked to mentions that it's already been checked in FF 7.0a1. Looks like FF releases really will be coming thick and fast.
N.b a comment from nutellajunkie on the Compatibility Reporter d/l page notes that there's an about:config tweak to do the same thing. Didn't say what it was but the bare mention made me curious enough to go digging. I found a very clear explanation of disabling the compatibility check with about:config here in Mozillazine.
Thanks again, fuller tips hat!
posted by jfuller at 3:53 PM on June 24, 2011
Dear god, I'm glad I don't work for MoFo. The shit they're getting for trying to Release Early And Often is amazing.
Firefox 3.x -> 4.x (well over a year apart) was a huge hassle. 4.x -> 5 (just a handful of weeks apart) is.... a huge hassle. I don't mind Release Early And Often, but if you're going to go for that, you have to be more sure that your changes are incremental rather than taking your chances with backward compatibility on every single 8-week update.
I have nearly as many add-ons in Chrome as on Firefox, and have yet to have the types of problems with Chrome updates that a full-point update of Firefox has proven to be.
Furthermore, what jfuller said is true. There are simpler browsers out there. There are lighter ones. There are faster ones. What Firefox has on these is its deep extensibility and extensive ecosystem. If they're going to shit in the add-on pool with every release, they're pretty much shooting themselves in the foot because it's add-ons that make Firefox superior to the other browsers.
posted by chimaera at 5:52 PM on June 24, 2011 [2 favorites]
Firefox 3.x -> 4.x (well over a year apart) was a huge hassle. 4.x -> 5 (just a handful of weeks apart) is.... a huge hassle. I don't mind Release Early And Often, but if you're going to go for that, you have to be more sure that your changes are incremental rather than taking your chances with backward compatibility on every single 8-week update.
I have nearly as many add-ons in Chrome as on Firefox, and have yet to have the types of problems with Chrome updates that a full-point update of Firefox has proven to be.
Furthermore, what jfuller said is true. There are simpler browsers out there. There are lighter ones. There are faster ones. What Firefox has on these is its deep extensibility and extensive ecosystem. If they're going to shit in the add-on pool with every release, they're pretty much shooting themselves in the foot because it's add-ons that make Firefox superior to the other browsers.
posted by chimaera at 5:52 PM on June 24, 2011 [2 favorites]
Is there someone that's still working on Scroll Tag? Because an update that works with the 'show new comments' feature would be so awesome.
posted by Gordafarin at 10:17 AM on June 25, 2011
posted by Gordafarin at 10:17 AM on June 25, 2011
psssst he's right behind you.
posted by gman at 10:23 AM on June 25, 2011 [1 favorite]
posted by gman at 10:23 AM on June 25, 2011 [1 favorite]
I also work for Mozilla.
When we released Firefox 5 on June 21, we worked hard with Add-on developers to ensure that over 80% of the Add-ons available at Mozilla's Add-ons site were compatible with Firefox 5. For those Add-ons that are not distributed via Mozilla's web site, we couldn't support those developers, unfortunately.
The reality is that browsers are increasingly important to everyone who uses the Internet and Mozilla could not continue doing major releases only once a year and still be competitive. Moving to 4X/year will ensure that new features will get to users sooner.
We are in a time when there is intense competition in the browser space and that means great software for everyone. This is a good thing. Whatever browser you choose to use, please do consider using the latest version.
posted by gen at 5:23 AM on June 27, 2011
When we released Firefox 5 on June 21, we worked hard with Add-on developers to ensure that over 80% of the Add-ons available at Mozilla's Add-ons site were compatible with Firefox 5. For those Add-ons that are not distributed via Mozilla's web site, we couldn't support those developers, unfortunately.
The reality is that browsers are increasingly important to everyone who uses the Internet and Mozilla could not continue doing major releases only once a year and still be competitive. Moving to 4X/year will ensure that new features will get to users sooner.
We are in a time when there is intense competition in the browser space and that means great software for everyone. This is a good thing. Whatever browser you choose to use, please do consider using the latest version.
posted by gen at 5:23 AM on June 27, 2011
At least for me, FF5 is faster and much more stable than 4 was. Our company runs our *nix /home directories out of NFS shares and FF4 really seemed to hate having it's profile files in a network share. 5 seems much happier.
posted by octothorpe at 5:33 AM on June 27, 2011
posted by octothorpe at 5:33 AM on June 27, 2011
Gordafarin: "Is there someone that's still working on Scroll Tag? Because an update that works with the 'show new comments' feature would be so awesome."
Yeah, I should do that.
posted by Plutor at 6:01 AM on June 27, 2011 [1 favorite]
Yeah, I should do that.
posted by Plutor at 6:01 AM on June 27, 2011 [1 favorite]
Proofs and Refutations: "Anyone got Multifavorited Multiwidth working with FF5? It's the only one that broke for me, but I miss it already."
Not working for me.
gen: " The reality is that browsers are increasingly important to everyone who uses the Internet and Mozilla could not continue doing major releases only once a year and still be competitive. Moving to 4X/year will ensure that new features will get to users sooner."
I wouldn't argue with that. What I would argue with is calling this petty little update an entirely new whole number instead of a 4.2 or 4.3.
posted by IndigoRain at 6:15 PM on June 27, 2011
Not working for me.
gen: " The reality is that browsers are increasingly important to everyone who uses the Internet and Mozilla could not continue doing major releases only once a year and still be competitive. Moving to 4X/year will ensure that new features will get to users sooner."
I wouldn't argue with that. What I would argue with is calling this petty little update an entirely new whole number instead of a 4.2 or 4.3.
posted by IndigoRain at 6:15 PM on June 27, 2011
It's okay, everybody. You can all relax.
I fixed mine.
posted by Deathalicious at 6:44 PM on June 27, 2011 [6 favorites]
I fixed mine.
posted by Deathalicious at 6:44 PM on June 27, 2011 [6 favorites]
Just to recap:
MultiFavorited Multiwidth is now working.
I'd like to take this opportunity to plug two other scripts:
Metafilter Heavy Discussion Count, which is like MultiFavorited Multiwidth, except this time identifying threads with lots of comments, and EasyMeMail which puts a little mailbox icon to everyone's username. Just click on it to go straight to a MeMail form for that user -- skips having to go to their contact page first. I had to do the same fix for Heavy Discussion Count, fortunately EasyMeMail still worked after the update.
posted by Deathalicious at 6:57 PM on June 27, 2011 [3 favorites]
MultiFavorited Multiwidth is now working.
I'd like to take this opportunity to plug two other scripts:
Metafilter Heavy Discussion Count, which is like MultiFavorited Multiwidth, except this time identifying threads with lots of comments, and EasyMeMail which puts a little mailbox icon to everyone's username. Just click on it to go straight to a MeMail form for that user -- skips having to go to their contact page first. I had to do the same fix for Heavy Discussion Count, fortunately EasyMeMail still worked after the update.
posted by Deathalicious at 6:57 PM on June 27, 2011 [3 favorites]
Scroll Tag now does the right thing with new comments retrieved via AJAX. You can get it from Gitorious or from UserScripts.
posted by Plutor at 10:26 AM on June 28, 2011 [3 favorites]
posted by Plutor at 10:26 AM on June 28, 2011 [3 favorites]
Thanks so much Deathalicious! I use Multifavorites a LOT to help me on super busy days and super long threads to zoom right in on notable comments!
posted by chimaera at 11:07 AM on June 28, 2011 [1 favorite]
posted by chimaera at 11:07 AM on June 28, 2011 [1 favorite]
"Metafilter Heavy Discussion Count"
Just a warning: There is a greasemonkey script out there with a very similar name but a remarkably different purpose, which makes for a rather... disturbing MetaFilter reading experience. Please type carefully when searching.
posted by Eideteker at 12:29 PM on June 28, 2011
Just a warning: There is a greasemonkey script out there with a very similar name but a remarkably different purpose, which makes for a rather... disturbing MetaFilter reading experience. Please type carefully when searching.
posted by Eideteker at 12:29 PM on June 28, 2011
Thank you Deathalicious, you made my day better. :) Just a side note, I was looking through your scripts and I didn't even know you wrote another of my favorites, Format Amazon Wishlist. Thanks again!
posted by IndigoRain at 1:09 PM on June 28, 2011
posted by IndigoRain at 1:09 PM on June 28, 2011
Just a warning: There is a greasemonkey script out there with a very similar name but a remarkably different purpose, which makes for a rather... disturbing MetaFilter reading experience. Please type carefully when searching.Don't be such a tease!
posted by Gordafarin at 2:20 PM on June 28, 2011
MeTa
Since this post is no longer on the MeTa front page, I just wanted to let others know that this has been fixed. Hopefully that's cool, otherwise it'll get closed and life will go on.
Thanks Deathalicious!
posted by marsha56 at 8:14 PM on June 28, 2011 [1 favorite]
Since this post is no longer on the MeTa front page, I just wanted to let others know that this has been fixed. Hopefully that's cool, otherwise it'll get closed and life will go on.
Thanks Deathalicious!
posted by marsha56 at 8:14 PM on June 28, 2011 [1 favorite]
Thanks for posting that in its own post, even though it got closed, I wouldn't have noticed it way down here.
posted by markr at 9:48 PM on June 28, 2011 [1 favorite]
posted by markr at 9:48 PM on June 28, 2011 [1 favorite]
Yeah, that's what I was thinking, but, oh well... Glad it helped.
posted by marsha56 at 10:20 PM on June 28, 2011
posted by marsha56 at 10:20 PM on June 28, 2011
Wow, my first ever positive callout. Predictably squashed. Yadda yadda all my life.
BTW, looks like userscripts is down; if anyone needs either GM script, just MeMail me.
posted by Deathalicious at 6:54 AM on June 30, 2011 [1 favorite]
BTW, looks like userscripts is down; if anyone needs either GM script, just MeMail me.
posted by Deathalicious at 6:54 AM on June 30, 2011 [1 favorite]
I fixed UserNotes and Welcome Back Mefite to work in Firefox 5, but can't upload them to userScripts for some reason: they are available at www.jacalata.com/greasemonkey for now.
posted by jacalata at 1:05 AM on July 1, 2011 [1 favorite]
posted by jacalata at 1:05 AM on July 1, 2011 [1 favorite]
« Older Generalissimo Fancisco Franco Is No Longer Dead | Butt Elephant is now the most recent search term Newer »
You are not logged in, either login or create an account to post comments
posted by Rhaomi at 5:56 PM on June 22, 2011