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 :))
Tomorrow, May 14, is the release date for Firefox 126.
These links will contain the usual bits of information for the new version once the release is live:
* release notes: https://www.mozilla.org/firefox/126.0/releasenotes/
* sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox126]
* complete list of changes: [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=target_milestone&o3=equals&v3=Firefox%20126&o1=equals&resolution=FIXED&o2=anyexact&query_format=advanced&f3=target_milestone&f2=cf_status_firefox126&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&v1=mozilla126&v2=fixed%2Cverified&limit=0]
* developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/126]
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 :))
I can't reproduce the issue from my end, so looking if anybody can confirm this.
Seems like a potential issue. We've got a number of people sharing about issue with Twitter after 126 update:
* https://twitter.com/Mouse140/status/1790634060538433988
* https://twitter.com/AI_Spam_404/status/1790731137813483840
* https://twitter.com/paul_wilson_nz/status/1790646345356984411
* https://twitter.com/Nicko_Realist/status/1790635862285533274
* https://www.reddit.com/r/firefox/comments/1ct87u2/twitter_stopped_working_on_os_x_firefox_esr/
* https://old.reddit.com/r/firefox/comments/1csg9gd/twitter_not_working_on_firefox/
I can't reproduce the issue from my end, so looking if anybody can confirm this.
This may not affect a lot of sites -- I think it may have been mentioned for Microsoft Office and Google Docs/Sheets -- but Firefox 126 finally supports the CSS zoom property by default.
This should enable website scripts to zoom content in Firefox more easily and more comparably with other browsers, but if the site has been using workarounds in Firefox (or hiding this feature based on user agent), users could see some odd behaviors when using sites' zoom features.
'''CSS zoom'''
This may not affect a lot of sites -- I think it may have been mentioned for Microsoft Office and Google Docs/Sheets -- but Firefox 126 finally supports the CSS zoom property by default.
This should enable website scripts to zoom content in Firefox more easily and more comparably with other browsers, but if the site has been using workarounds in Firefox (or hiding this feature based on user agent), users could see some odd behaviors when using sites' zoom features.
...I posted that this update cause my ad block to stop working...and its gone...why? This update was causing so many issues I installed 125...but Firefox would not let import every customization I made to it. Why?
...I posted that this update cause my ad block to stop working...and its gone...why? This update was causing so many issues I installed 125...but Firefox would not let import every customization I made to it. Why?
Seems like a potential issue. We've got a number of people sharing about issue with Twitter after 126 update:
Many said that changing ETP setting from Strict or disabling it altogether fix this issue. We've also notified the Firefox team to look into it.
''Kiki [[#post-87541|said]]''
<blockquote>
Seems like a potential issue. We've got a number of people sharing about issue with Twitter after 126 update:
</blockquote>
Many said that changing ETP setting from Strict or disabling it altogether fix this issue. We've also notified the Firefox team to look into it.
Hey folks, the team recognize the Twitter issue as an incident and they're currently working on a fix. If you see any questions around this, feel free to direct people to this thread, which we'll update once we have a more permanent resolution.
Thanks y'all!
Hey folks, the team recognize the Twitter issue as an incident and they're currently working on a fix. If you see any questions around this, feel free to direct people to [https://x.com/FirefoxSupport/status/1791365172571083193 this thread], which we'll update once we have a more permanent resolution.
Thanks y'all!
