firefox 44 seems to be rather light on user-facing changes - some stuff that might be relevant for sumo though:
redesigned/reworded certificate error pages. there is now a "learn more" link on those pages leading to the sumo article What do the security warning codes mean? (replacing the "this connection is untrusted" error from prior versions), which might generate quite a bit of traffic. we now have a dedicated article for interfering security products causing error messages on HTTPS pages where we could point affected users to as well: How to troubleshoot security error codes on secure websites
data from 44 release candidate builds show that trusteer rapport might be involved in some crashes particular for this version. ibm are usually quite quick in fixing their stuff, but until then maybe keep in mind that certain crashes (signatures: nsAppShell::ProcessNextNativeEvent, and some others containing MessagePump) might be caused by external factors and affected users could try deactivating/uninstalling rapport for the moment - Bug 1235257, Bug 1242393
please add to the thread as new things become available/known :-)
Firefox 44 is scheduled to be released later today, 2016-01-26
release notes: https://www.mozilla.org/en-US/firefox/44.0/releasenotes/
fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/
firefox 44 seems to be rather light on user-facing changes - some stuff that might be relevant for sumo though:
* '''redesigned/reworded certificate error pages'''. there is now a "learn more" link on those pages leading to the sumo article [[What does "Your connection is not secure" mean?]] (replacing the "this connection is untrusted" error from prior versions), which might generate quite a bit of traffic. we now have a dedicated article for interfering security products causing error messages on HTTPS pages where we could point affected users to as well: [[How to troubleshoot the error code "SEC_ERROR_UNKNOWN_ISSUER" on secure websites]]
* service worker improvements (including '''web push''') allow for improved website functionality: [[Web Push notifications in Firefox]]
* the "ask me everytime" option for cookies was removed from the privacy panel - [http://bgz.la/606655 Bug 606655]
* the addon signing enforcement has been moved back to firefox 46, so the ''xpinstall.signatures.required'' pref still works: https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/
known issues:
*data from 44 release candidate builds show that trusteer rapport might be involved in some crashes particular for this version. ibm are usually quite quick in fixing their stuff, but until then maybe keep in mind that certain crashes (signatures: ''nsAppShell::ProcessNextNativeEvent'', and some others containing ''MessagePump'') might be caused by external factors and affected users could try deactivating/uninstalling rapport for the moment - [http://bgz.la/1235257 Bug 1235257], [http://bgz.la/1242393 Bug 1242393]
please add to the thread as new things become available/known :-)
''philipp [[#post-68000|said]]''
<blockquote>
* the addon signing enforcement has been moved back to firefox 46, so the ''xpinstall.signatures.required'' pref still works: https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/
</blockquote>
To be more accurate this still only refers to Extensions. It was thought language packs was going to be included also.
https://wiki.mozilla.org/Addons/Extension_Signing#Timeline
Firefox 46: Release and Beta versions of Firefox will not allow unsigned '''extensions''' to be installed, with no override.
Linux users are noticing a slight theme change in Firefox 44.0 in which even with all black GTK 2 Themes it looks greyer compared to Firefox 43.0 ?
edit: Ok it is not just a Linux issue with Firefox 44.0.
Bug 1246005 - Some themes make the full tab bar with a gray overlay instead of gradient in Firefox 44
I can confirm users need GTK 3.4 installed and need GTK 3 Themes to theme Firefox as of Firefox 45.0b1. If a GTK 2 theme is in use Firefox 45.0b1 looks like it has no GTK Theme in use, just white. Bug 1227023#c41
Linux users are noticing a slight theme change in Firefox 44.0 in which even with all black GTK 2 Themes it looks greyer compared to Firefox 43.0 ?
edit: Ok it is not just a Linux issue with Firefox 44.0.
[https://bugzilla.mozilla.org/show_bug.cgi?id=1246005 Bug 1246005] - Some themes make the full tab bar with a gray overlay instead of gradient in Firefox 44
I can confirm users need GTK 3.4 installed and need GTK 3 Themes to theme Firefox as of Firefox '''45.0b1'''. If a GTK 2 theme is in use Firefox 45.0b1 looks like it has no GTK Theme in use, just white. [https://bugzilla.mozilla.org/show_bug.cgi?id=1227023#c41 Bug 1227023#c41]
And it looks like the need for GTK3 will be disabled as of 45.0b'''4'''.
https://blog.mozilla.org/meeting-notes/archives/2330
the password dataloss issue is going to be fixed with an hotfix-addon that is pushed out to firefox users. at the moment automatic updates are turned off anyway...
then there is another rather mysterious issue popping up in 44: some users are reporting that firefox is stuck on "connecting..." and not able to load webpages and there may be windows error reports when closing firefox. this seems to affect users with nvidia hardware so far & switching to 64bit versions of the browser apparently helps consistently.
sumo threads: https://support.mozilla.org/en-US/questions/firefox?tagged=44-connecting&show=all
i've put all my findings in Bug 1243765
the password dataloss issue is going to be fixed with an hotfix-addon that is pushed out to firefox users. at the moment automatic updates are turned off anyway...
then there is another rather mysterious issue popping up in 44: some users are reporting that firefox is stuck on "connecting..." and not able to load webpages and there may be windows error reports when closing firefox. this seems to affect users with nvidia hardware so far & switching to 64bit versions of the browser apparently helps consistently.
sumo threads: https://support.mozilla.org/en-US/questions/firefox?tagged=44-connecting&show=all
i've put all my findings in [https://bugzilla.mozilla.org/show_bug.cgi?id=1243765 Bug 1243765]
issue with cookies containing a space, this might fix login issues on particular websites: Bug 1244505
fix for some playback issues on youtube (audio/video out of sync for particular formats): Bug 1245696
there will be a update to 44.0.1 soon (i guess later today):
*the main driver is the password dataloss situation which can be handled more reliably with an update than with a hotfix addon: [https://bugzilla.mozilla.org/show_bug.cgi?id=1242176 Bug 1242176]
*two crash fixes: [https://bugzilla.mozilla.org/show_bug.cgi?id=1222171 Bug 1222171], [https://bugzilla.mozilla.org/show_bug.cgi?id=1244076 Bug 1244076]
*issue with cookies containing a space, this might fix login issues on particular websites: [https://bugzilla.mozilla.org/show_bug.cgi?id=1244505 Bug 1244505]
*fix for some playback issues on youtube (audio/video out of sync for particular formats): [https://bugzilla.mozilla.org/show_bug.cgi?id=1245696 Bug 1245696]
Fix a rare bug which triggered the removal of stored passwords (1242176)
Allows spaces in cookie names (1244505)
Fix a top crash in cache networking (1244076)
Fix WebSockets when used in a Service Worker context (1243942)
Disable opus/vorbis audio with H.264 (1245696)
Require NSS 3.21 (1244069)
Ship the Gecko SDK (1243740)
Fix for graphics startup crash (GNU/Linux) (1222171)
Firefox 44.0.1 Release Notes are up.
https://www.mozilla.org/firefox/44.0.1/releasenotes/
*Fix a rare bug which triggered the removal of stored passwords (1242176)
*Allows spaces in cookie names (1244505)
*Fix a top crash in cache networking (1244076)
*Fix WebSockets when used in a Service Worker context (1243942)
*Disable opus/vorbis audio with H.264 (1245696)
*Require NSS 3.21 (1244069)
*Ship the Gecko SDK (1243740)
*Fix for graphics startup crash (GNU/Linux) (1222171)
''ideato [[#post-68204|said]]''
<blockquote>
bug report ?
</blockquote>
no public one unfortunately, but the changes might soon show up here: https://hg.mozilla.org/releases/mozilla-release ...
if everything goes to plan 44.0.2 will be released tomorrow and also include a change that is hoped to fix the page loading/crash/windows error reports issue that popped up in 44 builds, i've raised before at #post-68046
if everything goes to plan 44.0.2 will be released tomorrow and also include a change that is hoped to fix the page loading/crash/windows error reports issue that popped up in 44 builds, i've raised before at [https://support.mozilla.org/en-US/forums/contributors/711796?last=68205#post-68046 #post-68046]
It appears 44.0.1 stub is blocked by smartscreen on Windows 10 from Edge. Maybe this is because they are already expecting 44.0.2.
I note smartscreen in Edge can be turned off in settings, and that the otherwise blocked file may then be downloaded.
Reported in question
* [/questions/1109203 Download blocked as unsafe by SmartScreen Filter in Windows10]
I think I'm up to 5 threads where Firefox doesn't load the user's home page at startup, just a blank page. In three threads, users said renaming or removing prefs.js resolved it, but "why" remains an unanswered question.
I think I'm up to 5 threads where Firefox doesn't load the user's home page at startup, just a blank page. In three threads, users said renaming or removing prefs.js resolved it, but "why" remains an unanswered question.
* [https://support.mozilla.org/questions/1108049 Firefox open with new tab not default home page]
* [https://support.mozilla.org/questions/1106790 When I open Firefox it does not go to my home page even though my setting are set to go to home page when Firefox is opened.]
* [https://support.mozilla.org/questions/1110224 I want my homepage to be https://startpage.com/. Firefox will not start up with this as my homepage no matter what I do.]
Suspected of being the same issue, but users haven't confirmed:
* [https://support.mozilla.org/questions/1110345 Firefox 44.0.2 problem loading Google as home page (in Win 7) ...]
* [https://support.mozilla.org/questions/1110736 yahoo will not open]
Anyone have any thoughts?
hey jscher, that issue might be bug 1243549 (fixed on 45).
and of similar nature (also apparently related to a failed sanitize on shutdown), but with firefox not responding in a new session: bug 248489
hey jscher, that issue might be [https://bugzilla.mozilla.org/show_bug.cgi?id=1243549 bug 1243549] (fixed on 45).
and of similar nature (also apparently related to a failed sanitize on shutdown), but with firefox not responding in a new session: [https://bugzilla.mozilla.org/show_bug.cgi?id=1248489 bug 248489]
''jscher2000 [[#post-68389|said]]''
<blockquote>
.... Anyone have any thoughts?
</blockquote>
I tried to suggest a workaround in
* [/questions/1110662 Would You Please Just Fix The Not Going To Homepage Issue With Firefox]
Please put back "ask me every time" for cookies. Even IE has this feature, it was working fine, and many of us depend on it for security.
You didn't even tell us, or ask us.
This move is really bad. Please put it back.
Please put back "ask me every time" for cookies. Even IE has this feature, it was working fine, and many of us depend on it for security.
You didn't even tell us, or ask us.
This move is really bad. Please put it back.
Please put back "ask me every time" for cookies. Even IE has this feature, it was working fine, and many of us depend on it for security.
You didn't even tell us, or ask us.
This move is really bad. Please put it back.
glnzSorry, but you are again posting in an inappropriate place.
We can not discuss developer issues here.
Kindly follow my suggestions in the support thread:
Next I must explain we are not developers we are fellow Firefox users. We can discus fixes and workarounds but not Developer's actions and decisions.
You may send a brief feedback comment. The information is analysed, partly automatically, and the results made available to Developers.
''glnz [[#post-68395|said]]''
<blockquote>
Please put back "ask me every time" for cookies. Even IE has this feature, it was working fine, and many of us depend on it for security.
You didn't even tell us, or ask us.
This move is really bad. Please put it back.
</blockquote>
'''glnz'''
'''Sorry, but you are again posting in an inappropriate place.'''
We can not discuss developer issues here.
Kindly follow my suggestions in the support thread:
''John99 [/questions/1110790 said]''
<blockquote>
Next I must explain we are not developers we are fellow Firefox users. We can discus fixes and workarounds but not Developer's actions and decisions.
You may send a brief feedback comment. The information is analysed, partly automatically, and the results made available to Developers.
* Use https://input.mozilla.org/feedback/firefox
</blockquote>
<blockquote>
glnz
Please do not discuss developer issues and decisions here.
Please use https://input.mozilla.org/feedback/firefox
Or please consider trying to find somewhere on
* https://www.mozilla.org/about/forums/
** Or on a third party site such as http://forums.mozillazine.org/
</blockquote>
