SUMO community discussions
Firefox 50 Release Notes / Issues / Discussions
-
Firefox 50 is scheduled to be released on 2016-11-15
release notes: https://www.mozilla.org/en-US/firefox/50.0/releasenotes/
fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox50 (to be disclosed at the time of release)
firefox 50 is going to be the last release in 2016 with an extra-long 10 week cycle to account for lower dev activity during the holiday season.
there is already a 50.1 bug fix release planned for mid-december (to address any stability issues or other regressions). in case there are critical chemspill releases necessary before that, they would be versioned as 50.0.x & afterwards as 50.1.x...
despite its round number, firefox 50 will be low on user facing changes but will try to win us over with its inner values:
- e10s will become enabled for more users who have addons which self-declare as compatible with the multi-process architecture (instead of the small whitelist we had in 49), which is expected to bring another 10% of release users to e10s. users can check if their addons are e10s compatible with the Compatibility Reporter extension which adds this information to about:addons
- e10s will now also bring its first security benefits, as on windows the content process (where web content runs) will be sandboxed by default (low integrity, level 1). this will also be indicated at the bottom of the about:support page - bug 1246505
- a performance bottleneck with the addon sdk was identified and fixed, which should lead to faster startup/shutdown time and lower memory consumption (tests showed the startup time improved by 35% for users without any addons; even more for users with addons) - https://blog.mozilla.org/nnethercote/.../faster-firefox-startup-shutdown-with-add-ons-present/, bug 1308332
- on windows 8 when it is detected that firefox is running on an account protected/restricted by windows family safety mode, it will automatically import the root certificates used by microsoft to monitor secure connections & activity on popular webpages, so that those users are spared the SEC_ERROR_UNKNOWN_ISSUER error by default - bug 1239166
- so far the crash rates on beta look quite promising, so 50 might become an extra stable release...
if there is more or new issues arise - as always - please feel free to add to the thread :))
Firefox 50 is scheduled to be released on 2016-11-15
release notes: https://www.mozilla.org/en-US/firefox/50.0/releasenotes/
fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox50 (to be disclosed at the time of release)
firefox 50 is going to be the last release in 2016 with an extra-long 10 week cycle to account for lower dev activity during the holiday season. <br>there is already a 50.1 bug fix release planned for mid-december (to address any stability issues or other regressions). in case there are critical chemspill releases necessary before that, they would be versioned as 50.0.x & afterwards as 50.1.x...
despite its round number, firefox 50 will be low on user facing changes but will try to win us over with its inner values:
* '''e10s will become enabled for more users''' who have '''addons which self-declare as compatible''' with the multi-process architecture (instead of the [https://support.mozilla.org/en-US/forums/contributors/712155?last=70641#post-70293 small whitelist] we had in 49), which is expected to bring another 10% of release users to e10s. users can check if their addons are e10s compatible with the [https://addons.mozilla.org/firefox/addon/add-on-compatibility-reporter/ Compatibility Reporter] extension which adds this information to about:addons
* e10s will now also bring its first security benefits, as on '''windows '''the '''content process '''(where web content runs) will be '''[https://wiki.mozilla.org/Security/Sandbox sandboxed]''' by default (low integrity, level 1). this will also be indicated at the bottom of the about:support page - [https://bugzilla.mozilla.org/show_bug.cgi?id=1246505 bug 1246505]
* a performance bottleneck with the addon sdk was identified and fixed, which should lead to '''faster startup/shutdown time''' and lower memory consumption (tests showed the startup time improved by 35% for users without any addons; even more for users with addons) - [https://blog.mozilla.org/nnethercote/2016/11/03/faster-firefox-startup-shutdown-with-add-ons-present/], [https://bugzilla.mozilla.org/show_bug.cgi?id=1308332 bug 1308332]
* on windows 8 when it is detected that firefox is running on an account protected/restricted by windows family safety mode, it will automatically import the root certificates used by microsoft to [https://support.mozilla.org/en-US/kb/troubleshoot-SEC_ERROR_UNKNOWN_ISSUER#w_family-safety-settings-in-windows-accounts monitor secure connections & activity on popular webpages], so that those users are spared the [https://support.microsoft.com/en-us/kb/2965142#bookmark-2 SEC_ERROR_UNKNOWN_ISSUER error] by default - [https://bugzilla.mozilla.org/show_bug.cgi?id=1239166 bug 1239166]
* so far the [https://crash-analysis.mozilla.com/release-mgmt/crash-report-tools/longtermgraph/?fxbeta crash rates] on beta look quite promising, so 50 might become an extra stable release...
if there is more or new issues arise - as always - please feel free to add to the thread :))
-
Some users have already reported input issues with USB keyboard devices. There are have only been a few reports already, but could this be a potential bug? Is anyone else able to replicate this issue?
Some users have already reported input issues with USB keyboard devices. There are have only been a few reports already, but could this be a potential bug? Is anyone else able to replicate this issue?
-
Hi Wesley
I have a USB keyboard but have not noticed problems and have had E10s active for a few versions now.
IIRC accessible devices and touchscreens were some of the problems initially preventing rollout of E10s so I guess it is plausible it could be an issue. Have you got links to the posts ?
How do we disable E10s any guides ?
I did post
John99 IN: Firefox runs in two instances in task manage
OK I am not certain of the correct exact method of disabling multi process Firefox but this is safe and works for me.
Back up the file prefs.js by making a copy and call it prefs.js.vo1
This is to make sure if anything goes wrong you have a simple method of reverting to the prior configuration. Key in to the address bar about:profiles press Enter key. Use the button [show profiles] to open your profile folder.
Close Firefox and make a copy of the file prefs.js rename that copy prefs.js.v01
Toggle the ...tabs.remote... prefs to false
Re open Firefox.
Key in about:config press Enter key
Look for the prefs that need changing. Key in on the search line bs.r wait a while for it to filter them. I see
browser.tabs.remote.autostart
browser.tabs.remote.autostart.2
browser.tabs.remote.desktopbehavior;false
Right click each one in turn, and use the Toggle option to set each to false
Restart Firefox so the change takes place.
You should then be in ordinary Firefox without multi process.
Use about:troubleshooting to check.
The Multiprocess Windows entry should start with a zero e.g.
Multiprocess Windows 0/1 (Disabled)
Hi Wesley
I have a USB keyboard but have not noticed problems and have had E10s active for a few versions now.
IIRC accessible devices and touchscreens were some of the problems initially preventing rollout of E10s so I guess it is plausible it could be an issue. Have you got links to the posts ?
How do we disable E10s any guides ?
I did post
''John99 [https://support.mozilla.org/en-US/questions/1147063#answer-936261 IN: Firefox runs in two instances in task manage]''
<blockquote>
OK I am not certain of the correct exact method of disabling multi process Firefox but this is safe and works for me.
<u>Back up the file prefs.js by making a copy and call it prefs.js.vo1 </u>
This is to make sure if anything goes wrong you have a simple method of reverting to the prior configuration. Key in to the address bar ''about:profiles'' press ''Enter'' key. Use the button [''show profiles''] to open your profile folder.
Close Firefox and make a copy of the file prefs.js rename that copy prefs.js.v01
<u>Toggle the ...tabs.remote... prefs to false </u>
Re open Firefox.
Key in ''about:config'' press ''Enter'' key
Look for the prefs that need changing. Key in on the search line ''bs.r'' wait a while for it to filter them. I see
browser.tabs.remote.autostart
browser.tabs.remote.autostart.2
browser.tabs.remote.desktopbehavior;false
Right click each one in turn, and use the ''Toggle'' option to set each to ''false''
Restart Firefox so the change takes place.
You should then be in ordinary Firefox without multi process.
Use about:troubleshooting to check.
The Multiprocess Windows entry should start with a zero e.g.
Multiprocess Windows 0/1 (Disabled)
</blockquote>
-
the only thing input-related so far that i have seen were chinese users crashing when they tried to switch from english input to a chinese ime - looks like there is already a patch for this particular crashing problem in place in 51, so to those users we recommend switching to the beta version at least...
the only thing input-related so far that i have seen were chinese users crashing when they tried to switch from english input to a chinese ime - looks like there is already a patch for this particular crashing problem in place in 51, so to those users we recommend switching to the beta version at least...
-
John99 said
How do we disable E10s any guides ?
I'm not sure if it is the recommended way, but setting extensions.e10sBlockedByAddons and browser.tabs.remote.force-enable to false should disable e10s. It basically tells Firefox that there is an add-on installed on the system that prevents e10s from running.
''John99 [[#post-70823|said]]''
<blockquote>How do we disable E10s any guides ?
</blockquote>
I'm not sure if it is the recommended way, but setting <code>extensions.e10sBlockedByAddons</code> and <code>browser.tabs.remote.force-enable</code> to <code>false</code> should disable e10s. It basically tells Firefox that there is an add-on installed on the system that prevents e10s from running.
-
RC4 support has been completely removed in Firefox 50 as it is no longer able to be overridden. https://www.fxsitecompat.com/en-CA/docs/2016/rc4-support-has-been-completely-removed/
RC4 support has been completely removed in Firefox 50 as it is no longer able to be overridden. https://www.fxsitecompat.com/en-CA/docs/2016/rc4-support-has-been-completely-removed/
-
Here's a question, what happened to the plugins update page?
Here's a question, what happened to the plugins update page?
-
Wesley Branton said
Here's a question, what happened to the plugins update page?
Nothing as it is still there https://www.mozilla.org/plugincheck/
''Wesley Branton [[#post-70848|said]]''
<blockquote>
Here's a question, what happened to the plugins update page?
</blockquote>
Nothing as it is still there https://www.mozilla.org/plugincheck/
-
hi wesley, the plugincheck page is getting deprioritized by mozilla - you can read up some background on this in bug 1277905.
since we will support flash as the only npapi plugin in firefox starting from version 52, there will be little usecases for it left as well...
hi wesley, the plugincheck page is getting deprioritized by mozilla - you can read up some background on this in [https://bugzilla.mozilla.org/show_bug.cgi?id=1277905 bug 1277905].
since we will support flash as the only npapi plugin in firefox starting from version 52, there will be little usecases for it left as well...
-
philipp said
hi wesley, the plugincheck page is getting deprioritized by mozilla - you can read up some background on this in bug 1277905.
since we will support flash as the only npapi plugin in firefox starting from version 52, there will be little usecases for it left as well...
I didn't even think of that. I guess you wouldn't need a plugin checker when there will be no plugins to check.
''philipp [[#post-70852|said]]''
<blockquote>
hi wesley, the plugincheck page is getting deprioritized by mozilla - you can read up some background on this in [https://bugzilla.mozilla.org/show_bug.cgi?id=1277905 bug 1277905].
since we will support flash as the only npapi plugin in firefox starting from version 52, there will be little usecases for it left as well...
</blockquote>
I didn't even think of that. I guess you wouldn't need a plugin checker when there will be no plugins to check.
-
Wesley Branton said
I didn't even think of that. I guess you wouldn't need a plugin checker when there will be no plugins to check.
But there still will be plugins to check for quite a while, though:
The next Firefox ESR (Extended Support Release) version is 52 and will receive security updates for a year. By removing NPAPI in Firefox 53, the release *after* the ESR, users that need NPAPI support can continue to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
The main reason why Firefox 53 is picked is that Firefox 52 is a new ESR release. This means that anyone on ESR will be able to use NPAPI plugins until that version is no longer used and that is not before May 2018
''Wesley Branton [[#post-70854|said]]''
<blockquote>
I didn't even think of that. I guess you wouldn't need a plugin checker when there will be no plugins to check.
</blockquote>
But there still will be plugins to check for quite a while, though:
The next Firefox ESR (Extended Support Release) version is 52 and will receive security updates for a year. By removing NPAPI in Firefox 53, the release *after* the ESR, users that need NPAPI support can continue to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
The main reason why Firefox 53 is picked is that Firefox 52 is a new ESR release. This means that anyone on ESR will be able to use NPAPI plugins until that version is no longer used and that is not before May 2018
-
Question about the new electrolysis, how stable is it, will FF Beta (windows) still crash/lag/high CPU usage when enabling it in about:config? Or is it already considered stable for daily use? :)
Question about the new electrolysis, how stable is it, will FF Beta (windows) still crash/lag/high CPU usage when enabling it in about:config? Or is it already considered stable for daily use? :)
-
It is being rolled out cautiously on Releases so it is deemed stable enough for ordinary users to use. However it is a new and complex feature and interacts with lots of other things and is bound to cause some problems, but unless people use it and test it those problems will not be discovered and fixed.
I suggest you try out the multi process mode initially without any addons active and if you find problems open a support question about them, and if they are definitely only occurring with electrolysis file a bug.
If electrolysis works for you the next step is to try it with addons enabled and I suggest the Compatibility Reporter extension { https://addons.mozilla.org/firefox/addon/add-on-compatibility-reporter/ ) that Philipp mentioned.
It is being rolled out cautiously on Releases so it is deemed stable enough for ordinary users to use. However it is a new and complex feature and interacts with lots of other things and is bound to cause some problems, but unless people use it and test it those problems will not be discovered and fixed.
I suggest you try out the multi process mode initially without any addons active and if you find problems open a support question about them, and if they are definitely only occurring with electrolysis file a bug.
If electrolysis works for you the next step is to try it with addons enabled and I suggest the Compatibility Reporter extension { https://addons.mozilla.org/firefox/addon/add-on-compatibility-reporter/ ) that Philipp mentioned.
-
Awesome extension! :) Just "reported" 2-3 addons that I disabled for now that are not working with multiprocess, but would like to use as soon as possible. :)
Awesome extension! :) Just "reported" 2-3 addons that I disabled for now that are not working with multiprocess, but would like to use as soon as possible. :)
-
Btw what is the "omni.ja" file exactly (that shows in taskmanager in the 2nd FF process :) ) Just trying to understand how e10s works. ;)
Btw what is the "omni.ja" file exactly (that shows in taskmanager in the 2nd FF process :) ) Just trying to understand how e10s works. ;)
-
It contains multiple Firefox resources see
It contains multiple Firefox resources see
* [https://developer.mozilla.org/docs/Mozilla/About_omni.ja_%28formerly_omni.jar%29 MDN: omni.ja (formerly omni.jar) ]
-
Wow nice! :) (Btw in MDN there is still a button "was this helpful?" missing! :D I'd have clicked it!)
Wow nice! :) (Btw in MDN there is still a button "was this helpful?" missing! :D I'd have clicked it!)
-
DanielNL said
Question about the new electrolysis, how stable is it, will FF Beta (windows) still crash/lag/high CPU usage when enabling it in about:config? Or is it already considered stable for daily use? :)
I have force enabled e10s on my Firefox and use it every day. I don't have any issues with crashing or lag.
''DanielNL [[#post-70858|said]]''
<blockquote>Question about the new electrolysis, how stable is it, will FF Beta (windows) still crash/lag/high CPU usage when enabling it in about:config? Or is it already considered stable for daily use? :)
</blockquote>
I have force enabled e10s on my Firefox and use it every day. I don't have any issues with crashing or lag.
-
Ok working fine when only using compatible add-ons! :) Awesome!
Ok working fine when only using compatible add-ons! :) Awesome!
-
Is there a place to read what will be new in Firefox Beta 52 ? :) I'm curious! (as I am on Beta 51.0 b1 currently)
Is there a place to read what will be new in Firefox Beta 52 ? :) I'm curious! (as I am on Beta 51.0 b1 currently)
