As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, post in the support forum instead pls :))
The coming week is release week for Firefox again - the go-live for Firefox 112 is scheduled for Tuesday, April 11.
These links will contain the usual bits of information for the new version:
* release notes: https://www.mozilla.org/firefox/112.0/releasenotes/
* sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox112]
* complete list of changes: https://mzl.la/3KGBKAx
* developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/112]
As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, [https://support.mozilla.org/questions/new post in the support forum instead] pls :))
''Paul [[#post-85252|said]]''
<blockquote>I'm seeing a fair bit of traffic about on getting Fx112, users are being logged out of sites.
</blockquote>
Maybe it is related to this:
https://blog.mozilla.org/en/mozilla/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/
Related articles:
* [[Introducing Total Cookie Protection in Standard Mode]]
* [[Total Cookie Protection and website breakage FAQ]]
Some examples:
https://matrix.to/#/!OjiTSQTpPWGpfDenKT:mozilla.org/$JXTcLUxJhH4m3bqKclduycN6qsBiZlIow3nzEpgVTaE?via=mozilla.org&via=matrix.org&via=privacytools.io
https://support.mozilla.org/en-US/questions/1410613
Hi Paul, there is a bug that seems to be related to a corrupted cookies.sqlite database -- the Manage Data dialog shows that the last use of cookies is many years in the future:
Hi Paul, there is a bug that seems to be related to a corrupted cookies.sqlite database -- the Manage Data dialog shows that the last use of cookies is many years in the future:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1827669 1827669 {Cookies} Severe cookies DB corruption...]
* https://www.reddit.com/r/firefox/comments/12j1whr/firefox_does_not_save_logins_after_update_to_1120/
* https://www.reddit.com/r/firefox/comments/12ijezp/firefox_1120_release_notes/jfynwf0/
A possible thing for users to check for are future dates in the right column:
[[Image:Manage Data dialog]]
----
More SUMO threads:
* https://support.mozilla.org/questions/1410665
* https://support.mozilla.org/questions/1410735
112.0.1 is out today. This should fix bug1827669 related to cookies that caused the log out issue (something that Paul and Jefferson previously discussed).
[https://www.mozilla.org/en-US/firefox/112.0.1/releasenotes/ 112.0.1] is out today. This should fix [https://bugzilla.mozilla.org/show_bug.cgi?id=1827669 bug1827669] related to cookies that caused the log out issue (something that Paul and Jefferson previously discussed).
112 and 112.0.1 are causing lots of Firefox icons to pop up into my Dock on Quit...literally hundreds of them which then use all of my processor cycles for 4-5 seconds.
112 and 112.0.1 are causing lots of Firefox icons to pop up into my Dock on Quit...literally hundreds of them which then use all of my processor cycles for 4-5 seconds.
112 and 112.0.1 are causing lots of Firefox icons to pop up into my Dock on Quit...literally hundreds of them which then use all of my processor cycles for 4-5 seconds.
This ismay be related to Bug 1827486 Firefox 112.0 leaving extra icon in macOS dock when "Delete cookies and site data when Firefox is closed" enabled (Fixed in Firefox 113)
''TonyC [[#post-85294|said]]''
<blockquote>
112 and 112.0.1 are causing lots of Firefox icons to pop up into my Dock on Quit...literally hundreds of them which then use all of my processor cycles for 4-5 seconds.
</blockquote>
This <s>is</s> <sub>may be related to </sub> [https://bugzilla.mozilla.org/show_bug.cgi?id=1827486 Bug 1827486] Firefox 112.0 leaving extra icon in macOS dock when "Delete cookies and site data when Firefox is closed" enabled <sub>(Fixed in Firefox 113)</sub>
Several Mac OS users are reporting a problem with not being able to exit video full screen using either the video player button or the Esc key. This seems to occur when the window was in full screen (either as a result of clicking the green button on the window frame or from using browser full screen).
It's not clear what the best workaround is for users who end up with a stuck tab.
Several Mac OS users are reporting a problem with not being able to exit video full screen using either the video player button or the Esc key. This seems to occur when the window was in full screen (either as a result of clicking the green button on the window frame or from using browser full screen).
Recent threads:
* https://support.mozilla.org/questions/1411250
* https://support.mozilla.org/questions/1411473
Relevant-sounding bugs:
* https://bugzilla.mozilla.org/show_bug.cgi?id=1829403 (newly opened)
* https://bugzilla.mozilla.org/show_bug.cgi?id=1824776 (closed during Nightly 113 cycle)
It's not clear what the best workaround is for users who end up with a stuck tab.
macOS 11.7.5 Big Sur and Firefox 112.0.1 - iMac (24-inch, M1, 2021)
I've tried watching several YouTube videos in full screen mode and the problem doesn't occur.
No problem even with beta 113.0b6 and Nightly 114.0a1.
@jscher2000 - Support Volunteer
macOS 11.7.5 Big Sur and Firefox 112.0.1 - iMac (24-inch, M1, 2021)
I've tried watching several YouTube videos in full screen mode and the problem doesn't occur.
No problem even with beta 113.0b6 and Nightly 114.0a1.
An issue has been identified that affects users who use a Fx theme with animations. If the users has an animated theme and multiple windows open with at least one of those windows being fully occluded, they will experience a slow in performance due to a leak that was accidentally introduce in Fx 112. The simple workaround is to switch to a theme without animations until the fix ships with Fx 112.0.2.
An issue has been identified that affects users who use a Fx theme with animations. If the users has an animated theme and multiple windows open with at least one of those windows being fully occluded, they will experience a slow in performance due to a leak that was accidentally introduce in Fx 112. The simple workaround is to switch to a theme without animations until the fix ships with Fx 112.0.2.
Bug for those interested - https://bugzilla.mozilla.org/show_bug.cgi?id=1828587
Also included in - https://www.mozilla.org/en-US/firefox/112.0.1/releasenotes/
Hey folks, have anyone notice issue with Twitter after the 112.0.2 release recently? We've seen a few questions similar to this or this on Twitter lately, but I couldn't find anything in Bugzilla.
Hey folks, have anyone notice issue with Twitter after the 112.0.2 release recently? We've seen a few questions similar to [https://twitter.com/QueenWarden48/status/1650479379699453953 this] or [https://twitter.com/RGBAtlantica/status/1651236186042581003 this] on Twitter lately, but I couldn't find anything in Bugzilla.
Hey folks, have anyone notice issue with Twitter after the 112.0.2 release recently? We've seen a few questions similar to this or this on Twitter lately, but I couldn't find anything in Bugzilla.
I don't usually use Twitter in a browser, but I checked right now and do not have those issues. I sign in using an email address (Twitter account). If the users encountering a problem are using a third party sign-in, maybe it is cookie issue.
''Kiki [[#post-85327|said]]''
<blockquote>
Hey folks, have anyone notice issue with Twitter after the 112.0.2 release recently? We've seen a few questions similar to [https://twitter.com/QueenWarden48/status/1650479379699453953 this] or [https://twitter.com/RGBAtlantica/status/1651236186042581003 this] on Twitter lately, but I couldn't find anything in Bugzilla.
</blockquote>
I don't usually use Twitter in a browser, but I checked right now and do not have those issues. I sign in using an email address (Twitter account). If the users encountering a problem are using a third party sign-in, maybe it is cookie issue.
I don't usually use Twitter in a browser, but I checked right now and do not have those issues. I sign in using an email address (Twitter account). If the users encountering a problem are using a third party sign-in, maybe it is cookie issue.
Thanks for testing it out, Jefferson. I don't experience the issue myself, so I initially thought that it's a platform issue. But good point, I may have to check first if they log in through a third-party service.
''jscher2000 - Support Volunteer [[#post-85328|said]]''
<blockquote>
I don't usually use Twitter in a browser, but I checked right now and do not have those issues. I sign in using an email address (Twitter account). If the users encountering a problem are using a third party sign-in, maybe it is cookie issue.
</blockquote>
Thanks for testing it out, Jefferson. I don't experience the issue myself, so I initially thought that it's a platform issue. But good point, I may have to check first if they log in through a third-party service.
Just in case life was getting boring, an issue has been identified where users of the paid for Avira antivirus is breaking website scripts, something that Avira have acknowledged is their fault.
Avira users should either wait until their Avira version updates to something strictly greater than 1.1.87.3 or they will need to disable HTTPS analysis within the Web Protection feature of Avira if they want to avoid the issue.
Just in case life was getting boring, an issue has been identified where users of the paid for Avira antivirus is breaking website scripts, something that Avira have acknowledged is their fault.
Avira users should either wait until their Avira version updates to something strictly greater than 1.1.87.3 or they will need to disable HTTPS analysis within the Web Protection feature of Avira if they want to avoid the issue.
Bug for those interested: https://bugzilla.mozilla.org/show_bug.cgi?id=1829925
