News for hackers. Stuff that matters.
Re:Firefox 57.0 Released by HenryBemis on Tuesday November 14, 2017 @06:22PM (#15700222)
It looked great, up to the point that 70% of my addons were disabled. I rolled back in 5mins :)

I'll give it another chance in a couple of weeks, and hope that there will be a bypass that will force my outdated addons to work.

Re:Firefox 57.0 Released by ajdlinux on Tuesday November 14, 2017 @06:25PM (#15700251)
There won't be a bypass - Fx57 has completely dropped legacy extension support.

This is a good thing, and it's just a shame that so many addons haven't been updated yet.

Re:Firefox 57.0 Released by ywain on Tuesday November 14, 2017 @06:55PM (#15700391)
This isn't quite true. Support for legacy extensions is disabled by default, but can be re-enabled via the `extensions.legacy.enabled` flag in about:config.
Re:Firefox 57.0 Released by rebelwebmaster on Tuesday November 14, 2017 @09:47PM (#15701118)
Don't expect it to work very well, though, given that a lot of the supporting code for legacy addons was already removed from Gecko 57.
Re:Firefox 57.0 Released by ajdlinux on Tuesday November 14, 2017 @08:33PM (#15700847)
Huh, thanks for mentioning that! I didn't realise there was still a flag for it - serves me right for not doing my research.

Though losing Electrolysis will defeat one of the main benefits of running Firefox 57...

Re:Firefox 57.0 Released by scholia on Tuesday November 14, 2017 @06:58PM (#15700407)
Though you lose multi-process operation, I think....
Re:Firefox 57.0 Released by branchless on Tuesday November 14, 2017 @10:41PM (#15701286)
only on incompatible MP plugins.

however I've just ran nightly and although it says vimfx will work as a legacy plugin it's not working, so the deal's off. I shall not use my mouse!

Re:Firefox 57.0 Released by mercurial on Wednesday November 15, 2017 @12:16AM (#15701623)
You can try vimium-ff (FF 57-compatible). There is also Tridactyl [1] currently in development.

1: https://github.com/cmcaine/tridactyl

Re:Firefox 57.0 Released by WCityMike on Tuesday November 14, 2017 @08:53PM (#15700905)
Only in Nightly.
Re:Firefox 57.0 Released by SllX on Wednesday November 15, 2017 @04:16AM (#15702502)
So while I'm still waiting on NoScript to get an update which is actually forthcoming (possibly tomorrow, but within about a week from what I gather), I took a look around to see which of my other add-ons were updated.

Other than a couple that were useful but ultimately not that important, and a couple I can do without until they get updated eventually, I managed to find that most of my Legacy extensions do have updated versions out. Namely, Video DownloadHelper and Greasemonkey, both extensions I thought would die with Firefox 57 out. That said, I wouldn't have known if I hadn't looked at the add-ons site as near as I can tell, while they still say "Legacy" in my Add-ons tab, they do have separate releases on the add-ons site specifically for Firefox 57 which are incompatible with my current browser and I'll probably have to install them again when I do update.* Assuming that is the case, you might find a decent chunk of that 70% already ready and you just have to take some extra steps to get them working again.

Overall, I am optimistic, lots of people have lots of nice things to say about 57 and the extensions situation is not looking nearly the sort of bad I was first expecting. I'm sure I've had more painful wait periods for my extensions going back almost a decade ago as it seems I really am waiting on just one and that one is coming shortly. Even those extensions which are now unsupported actually seem to have decent replacements and I've switched them over already.

* Note, this portion is entirely speculative, refer back to my commentary on waiting till an updated NoScript comes out before I actually install Firefox 57. It's possible they would just update once I do upgrade to 57 rendering my subsequent speculation entirely wrong.

Re:Firefox 57.0 Released by absove on Wednesday November 15, 2017 @08:03AM (#15703445)
Greasemonkey will be updated from legacy to the compatible one automatically, no user intervention needed. I assume this holds true for all such extensions.