-
September 30th, 2016, 04:52 PM
#1
Major Changes are coming for Firefox 52, 53, and 57
Firefox 52:
Release channel - drops support for NPAPI plugins except for Flash (Java, Silverlight, etc)
(ESR channel will retain NPAPI plugin support)
https://www.bleepingcomputer.com/new...-except-flash/
Firefox 53: (scheduled for release on April 18, 2017)
Drops support for XP and Vista
Firefox 57: (scheduled for release on November 28, 2017)
Drops support for XUL and XPCOM extensions
Firefox is transitioning to "web extensions". These will be similar to Google Chrome extensions. Note that web extension support has been gradually added since FF48.
http://www.ghacks.net/2016/11/24/fir...e-end-of-2017/
https://wiki.mozilla.org/WebExtensions/FAQ
Extensions that affect the UI, like Classic Theme Restorer, will no longer work.
Old extensions that are not maintained and/or ported to web extensions won't work either.
If an extension has a version that works in Google Chrome, it will probably be ported over to Firefox web extensions.
TLDNR: If you need to use XP or Vista, NPAPI plugins, or XUL/XPCOM extensions, you should transition to the ESR channel.
The easiest way is to just install the ESR version over the top of the Release version.
To manually change to the ESR channel, edit the channel-prefs.js file:
Make sure Firefox is CLOSED first
Open the Firefox program folder (Ex. C:\Program Files (x86)\Mozilla Firefox)
Open the defaults\prefs folder
Open channel-prefs.js with Notepad
Change pref("app.update.channel", "release"); to pref("app.update.channel", "esr");
Save channel-prefs.js
-
December 30th, 2016, 02:58 PM
#2
Does the ESR look and act just like regular FF?
Win7 Ult/ 3.40 GHZ Intel Core i5-3570K /ASRock mobo Z77 Pro4 /SSD/ EUFI MS 3400 MHZ/8 GB RAM; Win 7 Ult/Verizon FIOS wired network
Waterfox Classic/Chrome / Firefox 115esr
--------------------------------------------------------------------------------
"The medium is the message." - Marshall McLuhan
-
December 30th, 2016, 04:10 PM
#3
ESR stays on a certain version and only releases security updates. The current version is based on FF45. The next ESR will be based on FF52.
https://www.mozilla.org/en-US/firefo...nizations/faq/
-
March 5th, 2017, 11:05 PM
#4
I'm using Win 7 now anyway.
Win7 Ult/ 3.40 GHZ Intel Core i5-3570K /ASRock mobo Z77 Pro4 /SSD/ EUFI MS 3400 MHZ/8 GB RAM; Win 7 Ult/Verizon FIOS wired network
Waterfox Classic/Chrome / Firefox 115esr
--------------------------------------------------------------------------------
"The medium is the message." - Marshall McLuhan
-
March 5th, 2017, 11:44 PM
#5
And all extensions will be lost after v.56. So I'll probably move to SeaMonkey or ESR 52 anyway:
http://forums.mozillazine.org/viewto...?f=7&t=3027638
Win7 Ult/ 3.40 GHZ Intel Core i5-3570K /ASRock mobo Z77 Pro4 /SSD/ EUFI MS 3400 MHZ/8 GB RAM; Win 7 Ult/Verizon FIOS wired network
Waterfox Classic/Chrome / Firefox 115esr
--------------------------------------------------------------------------------
"The medium is the message." - Marshall McLuhan
-
March 7th, 2017, 03:24 AM
#6
Sorry about the error.
I think Chrome has a total of 30 extensions,some of them don't work, and their UI is naked. I used to like Opera as a fallback, then they redid it to look like Chrome. No, thanks.
Will I lose all the code tweaks I've done in the chrome folder, or will I just be unable to make new ones?
Win7 Ult/ 3.40 GHZ Intel Core i5-3570K /ASRock mobo Z77 Pro4 /SSD/ EUFI MS 3400 MHZ/8 GB RAM; Win 7 Ult/Verizon FIOS wired network
Waterfox Classic/Chrome / Firefox 115esr
--------------------------------------------------------------------------------
"The medium is the message." - Marshall McLuhan
-
March 6th, 2017, 05:48 AM
#7
Not ALL extensions; XUL and XPCOM based extensions. Basically, they are switching to web extensions which are going to be more like Chrome.
-
March 7th, 2017, 03:44 AM
#8
Google Chrome has hundreds of extensions, so I'm not sure where you got 30 from. Opera is now based on the same Webkit engine that Chrome used before (Chrome now uses Blink engine which is a fork of Webkit).
Will I lose all the code tweaks I've done in the chrome folder, or will I just be unable to make new ones?
Things like the userchrome.css won't work because Firefox won't have the XUL or XPCOM code in it. They mention it in the link you posted.
In the case of tweaks using user.Chrome.css, they will be gone.
-
March 11th, 2017, 03:02 PM
#9
From Train:
The bad news for Firefox users continues with the fact that the upcoming Firefox 53.0 release won't work on Linux computers powered by processors older than Pentium 4 or AMD Opteron, and 32-bit Mac OS X operating system won't be supported as Firefox is now distributed as a 64-bit only app for macOS Sierra or later.
http://news.softpedia.com/news/firef...n-513716.shtml
-
July 24th, 2017, 09:07 AM
#10
32-Bit Firefox Users on 64-Bit PCs Will Be Auto-Upgraded to 64-Bit Firefox
Mozilla engineers have decided that starting with Firefox 56 they will silently and forcibly auto-upgrade some users of 32-bit Firefox to 64-bit versions.
https://www.bleepingcomputer.com/new...4-bit-firefox/
-
July 24th, 2017, 04:08 PM
#11
If you prefer the 32-bit version, this is another reason to use ESR.
-
August 7th, 2017, 02:42 PM
#12
If you haven't migrated to ESR yet, now is the time to do it.
https://www.ghacks.net/2017/08/07/fi...t-what-is-new/
You cannot restore an older version / migrate to Firefox ESR after the upgrade to Firefox 55.
-
August 8th, 2017, 08:12 AM
#13
I have FireFox 54.01 and it's still 32 bit. Why didn't it change to 64 bit with the upgrade?
-
August 8th, 2017, 11:39 AM
#14
starting with Firefox 56 they will silently and forcibly auto-upgrade some users of 32-bit Firefox to 64-bit versions.
From post 10.
-
August 8th, 2017, 05:32 PM
#15
Thanks Train. I missed that altogether.
Thread Information
Users Browsing this Thread
There are currently 2 users browsing this thread. (0 members and 2 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|