Firefox 56.0.2 is EOL and is already behind on security fixes since.

https://www.mozilla.org/security/known-vulnerabilities/

Firefox 57.0.1 and Firefox 52 ESR are the only versions supported currently. Fx 52.5.0 is current with 52.5.2 coming (52.5.1esr was skipped due to issues) and 52.8.0esr out in May 2018 will likely be the last update.

The NoScript extension author does have updates for Firefox 57+ however it is still a work in progress.

https://addons.mozilla.org/firefox/addon/noscript/ https://hackademix.net/

James сказал(а)

Firefox 56.0.2 is EOL and is already behind on security fixes since. https://www.mozilla.org/security/known-vulnerabilities/ Firefox 57.0.1 and Firefox 52 ESR are the only versions supported currently. Fx 52.5.0 is current with 52.5.2 coming (52.5.1esr was skipped due to issues) and 52.8.0esr out in May 2018 will likely be the last update.

Thanks for the answer!

I don't think Firefox 52 ESR support multithreading. Without this, browser works really slow.

https://www.mozilla.org/en-US/security/advisories/mfsa2017-24/ I looked at the security fixes. Only some of them represent at least some kind of threat to me.

James сказал(а)

The NoScript extension author does have updates for Firefox 57+ however it is still a work in progress. https://addons.mozilla.org/firefox/addon/noscript/ https://hackademix.net/

NoScript I mentioned as some protection, which will help at least a little to secure an old version of the browser.

My problem in these extentions: Classic Theme Restorer Download Manager Tweak Menu Editor QuickProxy toggleDocuments Youtube Video and Audio Downloader

And everyone has their own list, which made this browser unique 9_9

booya said

Hello. I tried 57 and for me, it is very uncomfortable due to the fact that a large number of extensions not working anymore. And I can not spend much time looking for new versions of extensions or alternatives. I decided to use the old version for a few months or more (maybe 4-5 months). How dangerous is this? I'm using NoScript.

This is something you will have to decide. For me 3 of the 4 Addons updated and work but that is all I use. Either you contact those Addons for them to update to work with FF57 or there not much else that can be done.

booya said

I don't think Firefox 52 ESR support multithreading. Without this, browser works really slow.

Firefox 52 used one process for the browser and one process for content. The number of content processes was increased to 4 in Firefox 54.

Some extensions block multiprocess, but I'm not sure how to figure out the culprit if you run into that.

Certainly Firefox 57+ run faster than Firefox 52, but if you need the old extensions, well...

Either you contact those Addons for them to update to work with FF57 or there not much else that can be done.

The creators of these extensions already know about incompatibility, but I'm not sure that they will update and some of them like impossible (Classic Theme Restorer)

jscher2000 сказал(а)

Firefox 52 used one process for the browser and one process for content. The number of content processes was increased to 4 in Firefox 54.

I see. + in FF54 I can increase the number of processes for each additional tab, like 5 and more, like on this screenshot: http://distlinks.net/img/lnk/ff56multip-5.gif

This helped me a lot.

jscher2000 сказал(а)

Certainly Firefox 57+ run faster than Firefox 52, but if you need the old extensions, well...

Since version 54, I have no complaints about browser performance and functionality. And with this 57 ver. and incompatibility... The devs can say only ¯\_(ツ)_/¯

How can I do like this now? http://distlinks.net/img/lnk/ffcomflok56look.jpg

Me sad.

But thank you anyway.

Well can offer you these : https://addons.mozilla.org/en-US/firefox/extensions/ and https://mozilla.github.io/extension-finder/ so will have your new Extension alternatives lined up to go if and when decide to go to 57+. Version 57.0.2 is Current Release.

I too mourn the loss of my extensions, but with your limited time for "futzing around" my advice is to use your time for getting up-to-speed with Quantum Firefox 57. IOW, work towards a solution for the future rather get bogged down and mired in the past.

Classic Theme Restorer is dead, but Aris the developer of CTR so many years ago has provided a guide about how effect many features that were in CTR via userChrome.css.

And with the limitations for what extensions can and can't do, userChrome.css and its lesser know brother userContent.css is the "key" to living Firefox now and down the road if you want to modify the Firefox UI as extensions used to do. Aris - https://github.com/Aris-t2/CustomCSSforFx jscher2000 - https://www.userchrome.org/ and https://www.userchrome.org/adding-style-recipes-userchrome-css.html#namespaces

misc articles: https://fosspost.org/tutorials/how-to-customize-firefox-57-user-interface https://www.howtogeek.com/334716/how-to-customize-firefoxs-user-interface-with-userchrome.css/