SUMO community discussions

Firefox 105 for Desktop - Release Notes / Issues / Discussions

  • 14 Replies
  • Last reply by SUMOsJR
  • Locked
  1. philipp
    philipp 1304 posts
    more options

    Tomorrow, September 20, is the release day for Firefox 105.

    These links will contain the usual bits of information for the new version:

    As always feel free to add to this thread once you see more news or 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, September 20, is the release day for Firefox 105. These links will contain the usual bits of information for the new version: * release notes: https://www.mozilla.org/firefox/105.0/releasenotes/ * sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox105] * complete list of changes: https://mzl.la/3QUfxPl * developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/105] As always feel free to add to this thread once you see more news or 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 :))
  2. cor-el
    cor-el 1494 posts
    more options

    Note that Firefox 105 also got a fix for asus.com being on the HSTS preload list (issue with router.asus.com).

    Note that Firefox 105 also got a fix for asus.com being on the HSTS preload list (issue with router.asus.com). *[https://bugzilla.mozilla.org/show_bug.cgi?id=1788684 1788684] - Access to router.asus.com broken as of version 104
  3. philipp
    philipp 1304 posts
    more options

    The Firefox 91 ESR branch is now unsupported and users will receive the auto-update to version 102.3.0esr.

    The Firefox 91 ESR branch is now unsupported and users will receive the auto-update to version 102.3.0esr.
  4. jscher2000 - Support Volunteer
    jscher2000 - Support Volunteer 834 posts
    more options

    Firefox 105 places the cursor in the address bar rather than in the page when a user launches a new window (at startup or using Ctrl+N/Command+N). Example thread:

    https://support.mozilla.org/questions/1390064

    (Using the Home button in an existing tab doesn't seem to adopt this new behavior, but I've only tested lightly.)

    There is a bug on file about giving the user the option in Firefox 107, and potentially reverting the change in a Firefox 105 point release based on "overall feedback" (1784692).

    Can we create a bug1784692 tag for threads about this change?

    More threads:

    Firefox 105 places the cursor in the address bar rather than in the page when a user launches a new window (at startup or using Ctrl+N/Command+N). Example thread: https://support.mozilla.org/questions/1390064 (Using the Home button in an existing tab doesn't seem to adopt this new behavior, but I've only tested lightly.) There is a bug on file about giving the user the option in Firefox 107, and potentially reverting the change in a Firefox 105 point release based on "overall feedback" ([https://bugzilla.mozilla.org/show_bug.cgi?id=1784692 1784692]). '''Can we create a bug1784692 tag for threads about this change?''' '''''More threads:''''' * https://support.mozilla.org/questions/1390148

    Modified by jscher2000 - Support Volunteer on

  5. philipp
    philipp 1304 posts
    more options

    I tagged this one thread accordingly, so the tag should be available elsewhere too.

    I tagged this one thread accordingly, so the tag should be available elsewhere too.
  6. Kiki
    Kiki 1728 posts Mozilla Staff
    more options

    From bug 1784692

    The behavior will be reverted no later than October 4th.

    It seems that the team decided to revert the behavior sooner with the dot release 105.0.1.

    ''From bug 1784692'' <blockquote>The behavior will be reverted no later than October 4th. </blockquote> It seems that the team decided to revert the behavior sooner with the dot release 105.0.1.
  7. AliceWyman
    AliceWyman 6327 posts
    more options

    Firefox 105.0.1 has been released: https://www.mozilla.org/en-US/firefox/105.0.1/releasenotes/ Fixed: Reverted focus behavior for new windows back to the content area instead of the address bar (bug 1784692)

    Firefox 105.0.1 has been released: https://www.mozilla.org/en-US/firefox/105.0.1/releasenotes/ '''Fixed:''' Reverted focus behavior for new windows back to the content area instead of the address bar ([https://bugzilla.mozilla.org/show_bug.cgi?id=1784692 bug 1784692])
  8. Paul
    Paul 1311 posts
    more options

    Had a request from staff to find out if anyone is seeing any issues relating to PiP being asked about in the Forum or in Social.

    There is an indication that there may be an issue, but there is no info available to them to help establish what it is and what is causing it.

    If anyone hears of any issues, please get as much info about what is happening and post here.

    Had a request from staff to find out if anyone is seeing any issues relating to PiP being asked about in the Forum or in Social. There is an indication that there may be an issue, but there is no info available to them to help establish what it is and what is causing it. If anyone hears of any issues, please get as much info about what is happening and post here.
  9. NoahSUMO
    NoahSUMO 527 posts
    more options

    I haven't seen any issues about PiP yet but will let you know here if I see any.

    Although has anyone seen any issues regarding Chase.com? It will not load properly for me. The entire page layout is missing all the CSS styling elements & images. The only clue I have is I can see in the statusbar that its fighting like hell to get a TLS handshake. And it tries to grab it many times but fails (~30 or 50 times) then stops trying.

    This bank is literally one of the top 3 banks in the U.S. & it has international branches. So I'm really worried alot of people are hitting this. And it's consistently loading in a broken fashion for me. Its working fine on Fx 103 & below. Broken on Fx 104 & higher. Screenshot: https://ibb.co/Sd2QkJM

    Also seeing the broken page style look on CISA.gov (but only on certain areas not sitewide): Every page under this branch: https://www.cisa.gov/uscert/ A example broken page from the above branch: https://www.cisa.gov/uscert/ncas/current-activity/2022/09/21/mozilla-releases-security-updates-firefox-esr-thunderbird A 404 page but still incorrectly displayed in a broken fashion: https://www.cisa.gov/uscert/nav/report_phishing.html All the above pages load properly in Fx 104 & below. Screenshot: https://ibb.co/n14fJ7T

    I tried everything to get it load properly including Troubleshoot Mode & changing my useragent to Chrome as well. No addons are in my profile. It's a brand new profile. I disabled literally every protection that Firefox has (ETP, Total Cookie Protection & Cross-site cookie blocking, etc.) & still nothing. Grabbed a about:networking log for it too but that's about 70 MB. I'll file a bug but want to see if anyone else can reproduce this. Thanks!

    I haven't seen any issues about PiP yet but will let you know here if I see any. Although has anyone seen any issues regarding [https://chase.com Chase.com]? It will not load properly for me. The entire page layout is missing all the CSS styling elements & images. The only clue I have is I can see in the statusbar that its fighting like hell to get a TLS handshake. And it tries to grab it many times but fails (~30 or 50 times) then stops trying. This bank is literally one of the top 3 banks in the U.S. & it has international branches. So I'm really worried alot of people are hitting this. And it's consistently loading in a broken fashion for me. Its working fine on Fx 103 & below. Broken on Fx 104 & higher. Screenshot: https://ibb.co/Sd2QkJM Also seeing the broken page style look on CISA.gov (but only on certain areas not sitewide): Every page under this branch: https://www.cisa.gov/uscert/ A example broken page from the above branch: https://www.cisa.gov/uscert/ncas/current-activity/2022/09/21/mozilla-releases-security-updates-firefox-esr-thunderbird A 404 page but still incorrectly displayed in a broken fashion: https://www.cisa.gov/uscert/nav/report_phishing.html All the above pages load properly in Fx 104 & below. Screenshot: https://ibb.co/n14fJ7T I tried everything to get it load properly including Troubleshoot Mode & changing my useragent to Chrome as well. No addons are in my profile. It's a brand new profile. I disabled literally every protection that Firefox has (ETP, Total Cookie Protection & Cross-site cookie blocking, etc.) & still nothing. Grabbed a about:networking log for it too but that's about 70 MB. I'll file a bug but want to see if anyone else can reproduce this. Thanks!

    Modified by NoahSUMO on

  10. NoahSUMO
    NoahSUMO 527 posts
    more options

    Sorry all! False alarm. I thought I stumbled onto some new major regression that broke a big banking site that got me all excited. But I didn't. It turns out while I did all the troubleshooting I could on this, the problem was with a single pref called: network.http.sendRefererHeader. It was set to 0 instead of the default of 2.

    I'm honestly shocked it could break just loading a bank's homepage. I don't understand why it needs to know how I got to its homepage. It shouldn't need to know that. But I can imagine it breaking a bank site once you get past the login page. Many pages on that side of things would need to know what referred them there for security reasons I'm guessing.

    So while I wasted a lot of time on this, I'm glad I learned this lesson because network.http.sendRefererHeader could've been breaking a lot more things for me causing me to blame the failures on the wrong things.

    One epiphany I had afterwards was, why didn't Troubleshoot Mode disable this pref?! I thought it was suppose to disable a lot of privacy related prefs. I'll file a bug to force Troubleshoot Mode to disable network.http.sendRefererHeader or reset it. Although this pref did show up in the "Important Modified Preferences" list on the about:support page. But I did not look at it closely enough to spot it.

    Privacy workaround: I was able to fool Chase.com with this privacy pref instead: network.http.referer.spoofSource = True Cisa.gov does NOT fall for this though

    Sorry all! False alarm. I thought I stumbled onto some new major regression that broke a big banking site that got me all excited. But I didn't. It turns out while I did all the troubleshooting I could on this, the problem was with a single pref called: [https://wiki.mozilla.org/Security/Referrer network.http.sendRefererHeader]. It was set to 0 instead of the default of 2. I'm honestly shocked it could break just loading a bank's homepage. I don't understand why it needs to know how I got to its homepage. It shouldn't need to know that. But I can imagine it breaking a bank site once you get past the login page. Many pages on that side of things would need to know what referred them there for security reasons I'm guessing. So while I wasted a lot of time on this, I'm glad I learned this lesson because network.http.sendRefererHeader could've been breaking a lot more things for me causing me to blame the failures on the wrong things. One epiphany I had afterwards was, why didn't Troubleshoot Mode disable this pref?! I thought it was suppose to disable a lot of privacy related prefs. I'll file a bug to force Troubleshoot Mode to disable network.http.sendRefererHeader or reset it. Although this pref did show up in the "Important Modified Preferences" list on the about:support page. But I did not look at it closely enough to spot it. Privacy workaround: I was able to fool Chase.com with this privacy pref instead: [https://wiki.mozilla.org/Security/Referrer '''network.http.referer.spoofSource''' = '''True'''] Cisa.gov does NOT fall for this though
  11. AliceWyman
    AliceWyman 6327 posts
    more options

    Firefox 105.0.2 released: https://www.mozilla.org/en-US/firefox/105.0.2/releasenotes/

    Firefox 105.0.2 released: https://www.mozilla.org/en-US/firefox/105.0.2/releasenotes/
  12. Kiki
    Kiki 1728 posts Mozilla Staff
    more options

    Hi folks,

    Just a note that the team identified a high number of crash caused by Avast Antivirus (bug 1794064) and decided to have another dot release to fix it soon.

    Hi folks, Just a note that the team identified a high number of crash caused by Avast Antivirus ([https://bugzilla.mozilla.org/show_bug.cgi?id=1794064 bug 1794064]) and decided to have another dot release to fix it soon.
  13. AliceWyman
    AliceWyman 6327 posts
    more options

    Firefox 105.0.3 released October 7, 2022 https://www.mozilla.org/en-US/firefox/105.0.3/releasenotes/ (quote) Fixed Mitigated frequent crashes for Windows users with Avast or AVG Antivirus software installed (bug 1794064)

    Firefox 105.0.3 released October 7, 2022 https://www.mozilla.org/en-US/firefox/105.0.3/releasenotes/ (quote) '''Fixed''' Mitigated frequent crashes for Windows users with Avast or AVG Antivirus software installed ([https://bugzilla.mozilla.org/show_bug.cgi?id=1794064 bug 1794064])
  14. AliceWyman
    AliceWyman 6327 posts
    more options

    NoahSUMO said

    So while I wasted a lot of time on this, I'm glad I learned this lesson because network.http.sendRefererHeader could've been breaking a lot more things for me causing me to blame the failures on the wrong things. One epiphany I had afterwards was, why didn't Troubleshoot Mode disable this pref?! I thought it was suppose to disable a lot of privacy related prefs.

    Firefox preference settings are not disabled in Troubleshoot Mode. See Use Troubleshoot Mode in Firefox under The problem happens in Troubleshoot Mode.

    ''NoahSUMO [[#post-84299|said]]'' <blockquote> So while I wasted a lot of time on this, I'm glad I learned this lesson because network.http.sendRefererHeader could've been breaking a lot more things for me causing me to blame the failures on the wrong things. One epiphany I had afterwards was, why didn't Troubleshoot Mode disable this pref?! I thought it was suppose to disable a lot of privacy related prefs. </blockquote> Firefox preference settings are not disabled in Troubleshoot Mode. See [[Diagnose Firefox issues using Troubleshoot Mode]] under '''The problem happens in Troubleshoot Mode'''.
  15. SUMOsJR
    SUMOsJR 196 posts Mozilla Staff
    more options

    Thanks everyone for your notes on what users have been running into this release.

    Thanks everyone for your notes on what users have been running into this release.