Firefox 51 is the first release in 2017. It is planned to increase the e10s population again - e10s should be on by default now for all users with no addons explicitly stating that they are multiprocess-incompatible.
Also related to passwords: Users can now tick a box to make their password visible while entering it in the doorhanger panel - Bug 1270321
On domains where users have set a non-default zoom level, this will now be indicated at the right of the address bar. Users can also reset the level to 100% by clicking on that indicator - Bug 565718
Media embedded in background tabs won't start to play automatically anymore unless the user is switching to that tab. This can be changed back to the old behaviour by flipping the media.block-autoplay-until-in-foreground preference back to false. In 52 this will become more useful as an icon is getting added to the affected tabs - Bug 1262053edit: feature not ready for 51, it will be pref'd off by default
The download doorhanger panel is getting a bit of an overhaul - Bug 1269956 sorry, this is also not landing in 51 and scheduled for 52
Support for the FLAC audio codec got implemented - Bug 1195723
...and as always, if there are changes or new issues arise, please feel free to add to this thread :))
Firefox 51 is scheduled to be released on 2017-01-24
release notes: https://www.mozilla.org/en-US/firefox/51.0/releasenotes/
fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox51 (to be disclosed at the time of release)
Firefox 51 is the first release in 2017. It is planned to increase the e10s population again - e10s should be on by default now for all users with no addons explicitly stating that they are multiprocess-incompatible.
Some notable changes in 51 are:
* The site security icon warns people when they are on an (insecure) HTTP-connection with a password box: '''[[Insecure password warning in Firefox]]''' - [https://bugzilla.mozilla.org/show_bug.cgi?id=1319119 Bug 1319119]
* Also related to passwords: Users can now tick a box to '''make their password visible''' while entering it in the doorhanger panel - [https://bugzilla.mozilla.org/show_bug.cgi?id=1270321 Bug 1270321]
* On domains where users have set a '''non-default zoom level''', this will now be '''indicated '''at the right of the address bar. Users can also reset the level to 100% by clicking on that indicator - [https://bugzilla.mozilla.org/show_bug.cgi?id=565718 Bug 565718]
* <s>'''Media embedded in background tabs won't start to play automatically''' anymore unless the user is switching to that tab. This can be changed back to the old behaviour by flipping the ''media.block-autoplay-until-in-foreground'' preference back to ''false''. In 52 this will become more useful as an [https://bugzilla.mozilla.org/show_bug.cgi?id=1308153 icon] is getting added to the affected tabs - [https://bugzilla.mozilla.org/show_bug.cgi?id=1262053 Bug 1262053]</s> ''edit: feature not ready for 51, it will be pref'd off by default''
* <s>The '''download doorhanger panel''' is getting a bit of an overhaul - [https://bugzilla.mozilla.org/show_bug.cgi?id=1269956 Bug 1269956]</s> sorry, this is also not landing in 51 and scheduled for 52
* Support for the '''FLAC audio codec''' got implemented - [https://bugzilla.mozilla.org/show_bug.cgi?id=1195723 Bug 1195723]
* And finally: The build architecture will be put into ''Help > About Firefox'' which makes it easier for users to [[How do I tell if I have the 32-bit or 64-bit Firefox?|tell if they have the 32-bit or 64-bit version of Firefox]] - [https://bugzilla.mozilla.org/show_bug.cgi?id=597738 Bug 597738]
...and as always, if there are changes or new issues arise, please feel free to add to this thread :))
Related bug (status-firefox51: affected → fixed):
Bug 1309707 - Distrust new certs chaining up to current WoSign/StartCom roots
I noticed that Joni has a new canned response pending approval:
[[Forum response - Some websites won't load after updating to version 51]]
The [https://support.mozilla.org/en-US/kb/forum-response-websites-wont-load-after-update-51/revision/137446 revision content] links to [https://blog.mozilla.org/security/2016/10/24/distrusting-new-wosign-and-startcom-certificates/ this security blog post].
Related bug (status-firefox51: affected → fixed):
[https://bugzilla.mozilla.org/show_bug.cgi?id=1309707 Bug 1309707] - Distrust new certs chaining up to current WoSign/StartCom roots
it won't be necessary to fiddle with addons - reloadevery for example doesn't contain any information if it is compatible or incompatible with multiprocess-firefox. so as per the new policy in 51, it won't block the enabling of e10s in your profile any more.
if you want to force on e10s regardless of the state of your addons, you can also set the preference extensions.e10sBlocksEnabling to false in about:config.
it won't be necessary to fiddle with addons - reloadevery for example doesn't contain any information if it is compatible or incompatible with multiprocess-firefox. so as per the new policy in 51, it won't block the enabling of e10s in your profile any more.
if you want to force on e10s regardless of the state of your addons, you can also set the preference ''extensions.e10sBlocksEnabling'' to ''false'' in about:config.
ok, i have to backtrack on that initial e10s claim already. apparently e10s use in firefox 51 will be expanded to users who have whitelisted addons - the whitelist consists of addons that have more than 100 users on the beta channel and doesn't explicitly claim it's incompatible with multiprocess: https://bugzilla.mozilla.org/show_bug.cgi?id=1329015
ok, i have to backtrack on that initial e10s claim already. apparently e10s use in firefox 51 will be expanded to users who have whitelisted addons - the whitelist consists of addons that have more than 100 users on the beta channel and doesn't explicitly claim it's incompatible with multiprocess: https://bugzilla.mozilla.org/show_bug.cgi?id=1329015
Can addons be modified e10 compatible by others or only by the original addon developer?
Most free extensions have a permissive open source license allowing anyone to create a derivative version, but there are exceptions.
''DanielNL [[#post-71297|said]]''
<blockquote>
Can addons be modified e10 compatible by others or only by the original addon developer?
</blockquote>
Most free extensions have a permissive open source license allowing anyone to create a derivative version, but there are exceptions.
geolocation seems broken in 51, automatic background updates will be halted until this is investigated - https://bugzilla.mozilla.org/show_bug.cgi?id=1333516
ok, i have to backtrack on that initial e10s claim already. apparently e10s use in firefox 51 will be expanded to users who have whitelisted addons - the whitelist consists of addons that have more than 100 users on the beta channel and doesn't explicitly claim it's incompatible with multiprocess: https://bugzilla.mozilla.org/show_bug.cgi?id=1329015
Clarified today that 52 will only have touch enabled for 32bit users with Windows 8 and Windows 10
''philipp [[#post-71306|said]]''
<blockquote>
ok, i have to backtrack on that initial e10s claim already. apparently e10s use in firefox 51 will be expanded to users who have whitelisted addons - the whitelist consists of addons that have more than 100 users on the beta channel and doesn't explicitly claim it's incompatible with multiprocess: https://bugzilla.mozilla.org/show_bug.cgi?id=1329015
</blockquote>
Clarified today that 52 will only have touch enabled for 32bit users with Windows 8 and Windows 10
51.0.1 is getting released now which fixes the geolocation bug, some of the crashes with websense and fixes a bug where the e10s-whitelist for addons did overwrite the incompatibility flag that extensions could set themselves (which broke amazon assistant for example)
51.0.1 is getting released now which fixes the geolocation bug, some of the crashes with websense and fixes a bug where the e10s-whitelist for addons did overwrite the incompatibility flag that extensions could set themselves (which broke amazon assistant for example)
it was no chemspill (this would be a critical security update with no ridealong). i've listed all that changed in my prior post. apparently there were no partials generated for the update from 51.0->51.0.1, which is the only reason for the size of the update you received: https://archive.mozilla.org/pub/firefox/releases/51.0.1/update/win32/en-US/
it was no chemspill (this would be a critical security update with no ridealong). i've listed all that changed in my prior post. apparently there were no partials generated for the update from 51.0->51.0.1, which is the only reason for the size of the update you received: https://archive.mozilla.org/pub/firefox/releases/51.0.1/update/win32/en-US/
forcepoint/websense security software still causes problems with new firefox versions (in the form of startup crashes). this is now noted in the firefox release notes as well & we have this article that we can share with affected users: Old versions of Websense cause startup crashes in Firefox
two more issues worth noting:
* firefox 51 will no longer trust certificates from wosign and startssl: https://blog.mozilla.org/security/2016/10/24/distrusting-new-wosign-and-startcom-certificates/ - we also have a canned response for that: [[Forum response - Some websites won't load after updating to version 51]]
* forcepoint/websense security software still causes problems with new firefox versions (in the form of startup crashes). this is now noted in the firefox release notes as well & we have this article that we can share with affected users: [[Old versions of Websense cause startup crashes in Firefox]]
What about the ReloadEvery addon, philipp? I tried it today, doesn't work (still says incompatible). :/ Also what do you guys think of my new feature idea? :) https://img4.picload.org/image/roolaacw/fffeature.png
What about the ReloadEvery addon, philipp? I tried it today, doesn't work (still says incompatible). :/ Also what do you guys think of my new feature idea? :) https://img4.picload.org/image/roolaacw/fffeature.png
No problems here with moving the Bookmarks Toolbar items to the left end of the Navigation Toolbar.
Note that there is a special nav-bar-customization-target container and items need to be in this container.
Extensions can place their icon outside this container in a fixed position and do not show when you enter customization mode.
No problems here with moving the Bookmarks Toolbar items to the left end of the Navigation Toolbar.
Note that there is a special nav-bar-customization-target container and items need to be in this container.
Extensions can place their icon outside this container in a fixed position and do not show when you enter customization mode.
cor-el can you make a video, showing what you mean? (I don't quite understand how you can place bookmarks in different positions? I thought there can only be one "bookmark toolbar" ?)
cor-el can you make a video, showing what you mean? (I don't quite understand how you can place bookmarks in different positions? I thought there can only be one "bookmark toolbar" ?)
there are a number of reports of users with the Microsoft Enhanced Mitigation Experience Toolkit (EMET) that constantly receive "Bad news: This tab has crashed" messages after the update to firefox 51.
apparently fiddling with the SEHOP settings in the tool can rectify the situation according to one affected user - bug 1335086
there are a number of reports of users with the Microsoft Enhanced Mitigation Experience Toolkit (EMET) that constantly receive "Bad news: This tab has crashed" messages after the update to firefox 51.
apparently fiddling with the SEHOP settings in the tool can rectify the situation according to one affected user - [https://bugzilla.mozilla.org/show_bug.cgi?id=1335086 bug 1335086]
https://support.mozilla.org/questions/firefox?tagged=bug1335086&show=all
Also does anyone know if we finally get the new context option "open image in new tab" on right click on images on websites in Firefox Beta 4 or 5 ? :)
Also does anyone know if we finally get the new context option "open image in new tab" on right click on images on websites in Firefox Beta 4 or 5 ? :)
