SUMO community discussions

Firefox 136 for Desktop - Release Notes / Issues / Discussions

  1. Tomorrow, March 4, is the release date for Firefox 136.

    These links will contain the usual bits of information for the new version once the release is live:

    As always feel free to add to this thread if you see other news or common problems popping up with the new 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, March 4, is the release date for Firefox 136. 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/136.0/releasenotes/ * sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox136] * complete list of changes: [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=target_milestone&o3=equals&v3=Firefox%20136&o1=equals&resolution=FIXED&o2=anyexact&query_format=advanced&f3=target_milestone&f2=cf_status_firefox136&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&v1=mozilla136&v2=fixed%2Cverified&limit=0] * developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/136] As always feel free to add to this thread if you see other news or common problems popping up with the new 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. Pocket off Pocket on again It's almost like a new install. I had to change a lot of settings back to what I had set.  ;-((

    [[Image:Pocket off]] [[Image:Pocket on again]] It's almost like a new install. I had to change a lot of settings back to what I had set. ;-((

    Modified by jonzn4SUSE on

  3. Was anyone else completely unimpressed and irrritated as F**K, with the most recent updates Firefox rolled out on the PC Web Browser for Version 136?

    Was anyone else completely unimpressed and irrritated as F**K, with the most recent updates Firefox rolled out on the PC Web Browser for Version 136?

    Modified by Brenneca on

  4. Brenneca said

    Was anyone else completely unimpressed and irrritated as F**K, with the most recent updates Firefox rolled out on the PC Web Browser for Version 136?

    What changes irritated you? If you have a question about settings or workarounds for that, please post a question on the support forum:

    https://support.mozilla.org/questions/new/desktop/form

    ''Brenneca [[#post-88655|said]]'' <blockquote> Was anyone else completely unimpressed and irrritated as F**K, with the most recent updates Firefox rolled out on the PC Web Browser for Version 136? </blockquote> What changes irritated you? If you have a question about settings or workarounds for that, please post a question on the support forum: https://support.mozilla.org/questions/new/desktop/form
  5. Btw a new change for Releases as of Firefox 136.0

    from https://www.mozilla.org/firefox/136.0/releasenotes/

    On Linux, Firefox is now available on ARM64 (AArch64), with installation options via APT and tarballs. Flatpak support is coming soon

    https://www.mozilla.org/firefox/all/desktop-release/

    Btw a new change for Releases as of Firefox 136.0 from https://www.mozilla.org/firefox/136.0/releasenotes/ <blockquote>On Linux, Firefox is now available on ARM64 (AArch64), with installation options via APT and tarballs. Flatpak support is coming soon</blockquote> https://www.mozilla.org/firefox/all/desktop-release/
  6. https://www.mozilla.org/firefox/136.0.1/releasenotes/

    Fixed Fixed an issue where a cookie size limit caused problems with website cookie management when using the CookieStore API. This could cause login and other state-related issues. (Bug 1950565) Fixed an issue where Control/Command+L did not focus the address bar in new windows. (Bug 1947723)
    https://www.mozilla.org/firefox/136.0.1/releasenotes/ <blockquote>Fixed Fixed an issue where a cookie size limit caused problems with website cookie management when using the CookieStore API. This could cause login and other state-related issues. (Bug 1950565) Fixed an issue where Control/Command+L did not focus the address bar in new windows. (Bug 1947723)</blockquote>
  7. Hi folks,

    I have updated the wiki for Firefox 136 to include several incidents on desktop and iOS. Please keep an eye on it!

    Hi folks, I have updated the [https://wiki.mozilla.org/Support/Firefox136 wiki for Firefox 136] to include several incidents on desktop and iOS. Please keep an eye on it!
  8. [Important notice] The root certificate in old Firefox versions on desktop and Android expires today! Users impacted by this (those using version < 128 and ESR < 115.13) will likely notice that their extensions will stop working. Some other settings will stop working too, but users aren't likely to notice them. It may take up 24 hours before add-ons are disabled in affected Firefox versions.

    Please see here for more information.

    '''[Important notice] The root certificate in old Firefox versions on desktop and Android expires today! ''' Users impacted by this (those using version < 128 and ESR < 115.13) will likely notice that their extensions will stop working. Some other settings will stop working too, but users aren't likely to notice them. It may take up 24 hours before add-ons are disabled in affected Firefox versions. Please see [/forums/contributors/717137?last=88706#post-88701 here] for more information.
  9. People are now posting about their Extensions are being disabled with message of "Extension name could not be verified for use in Firefox version and has been disabled".

    edit: Those using a version that is not Firefox 128 or later or Firefox 115.13.0esr or later and try to install a Extension will get a message of ""installation aborted because the add-on appears to be corrupt"

    People are now posting about their Extensions are being disabled with message of "Extension name could not be verified for use in Firefox version and has been disabled". edit: Those using a version that is not Firefox 128 or later or Firefox 115.13.0esr or later and try to install a Extension will get a message of ""installation aborted because the add-on appears to be corrupt"

    Modified by James (doing minimal support) on

  10. Hi, Several users with FX 136 have problems with extensions With error: "Extension name could not be verified for use in Firefox version and has been disabled": https://support.mozilla.org/es/questions/1498807 https://support.mozilla.org/es/questions/1499691

    To install a Extension
    

    "installation aborted because the add-on appears to be corrupt" https://support.mozilla.org/es/questions/1499605

    Hi, Several users with FX 136 have problems with extensions With error: "Extension name could not be verified for use in Firefox version and has been disabled": https://support.mozilla.org/es/questions/1498807 https://support.mozilla.org/es/questions/1499691 To install a Extension "installation aborted because the add-on appears to be corrupt" https://support.mozilla.org/es/questions/1499605
  11. more options

    See https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox/history revision comment: Link to relevant SUMO page; a user encountering this issue mentioned this kb page at https://old.reddit.com/r/firefox/comments/1jbhi1v/how_do_i_reenable_extensions_that_are_not/

    The revision to the Add-on signing in Firefox article was to add the following to the What can I do if Firefox disables an installed add-on? section: If all of your add-ons have been disabled, your Firefox version may be out of date. See Update Firefox to prevent add-ons issues from root certificate expiration.

    P.S. I submitted a revision that's pending, to the Re-enable add-ons that were disabled when updating Firefox article Intro note, to add a link to the root certificate expiration article. Can someone review my revision? See https://support.mozilla.org/en-US/kb/re-enable-add-ons-disabled-when-updating/history

    See https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox/history revision comment: Link to relevant SUMO page; a user encountering this issue mentioned this kb page at https://old.reddit.com/r/firefox/comments/1jbhi1v/how_do_i_reenable_extensions_that_are_not/ The revision to the [[Add-on signing in Firefox]] article was to add the following to the '''What can I do if Firefox disables an installed add-on?''' section: If all of your add-ons have been disabled, your Firefox version may be out of date. See [[Update Firefox to prevent add-ons issues from root certificate expiration]]. P.S. I submitted a revision that's pending, to the [[Re-enable add-ons that were disabled when updating Firefox]] article Intro note, to add a link to the root certificate expiration article. Can someone review my revision? See https://support.mozilla.org/en-US/kb/re-enable-add-ons-disabled-when-updating/history

    Modified by AliceWyman on

  12. AliceWyman ha detto

    P.S. I submitted a revision that's pending, to the Re-enable add-ons that were disabled when updating Firefox article Intro note, to add a link to the root certificate expiration article. Can someone review my revision? See https://support.mozilla.org/en-US/kb/re-enable-add-ons-disabled-when-updating/history
    Done ;)
    ''AliceWyman [[#post-88742|ha detto]]'' <blockquote>P.S. I submitted a revision that's pending, to the [[Re-enable add-ons that were disabled when updating Firefox]] article Intro note, to add a link to the root certificate expiration article. Can someone review my revision? See https://support.mozilla.org/en-US/kb/re-enable-add-ons-disabled-when-updating/history </blockquote> Done ;)
  13. Firefox 136.0.2 update. https://www.mozilla.org/firefox/136.0.2/releasenotes/

    Fixed Fixed a bug where "Cookies and site data" and "Temporary cached files and pages" were unexpectedly enabled after updating to Firefox 136 for users with "History" and/or "Site settings" set to clear on shutdown in previous versions. (Bug 1952564) Affected users already on Firefox 136 can disable these settings in "Privacy & Security". Fixed an issue where the Primary Password prompt appeared in unexpected situations. (Bug 1946121) Fixed visibility issues with radio buttons on dark backgrounds. (Bug 1951930) Fixed high CPU usage on Windows when the screen was locked or the laptop lid was closed. (Bug 1924932) Web Platform Disabled support for the CookieStore API due to compatibility concerns. The API will be enabled later once the compatibility issues have been addressed.
    Firefox 136.0.2 update. https://www.mozilla.org/firefox/136.0.2/releasenotes/ <blockquote>Fixed Fixed a bug where "Cookies and site data" and "Temporary cached files and pages" were unexpectedly enabled after updating to Firefox 136 for users with "History" and/or "Site settings" set to clear on shutdown in previous versions. (Bug 1952564) Affected users already on Firefox 136 can disable these settings in "Privacy & Security". Fixed an issue where the Primary Password prompt appeared in unexpected situations. (Bug 1946121) Fixed visibility issues with radio buttons on dark backgrounds. (Bug 1951930) Fixed high CPU usage on Windows when the screen was locked or the laptop lid was closed. (Bug 1924932) Web Platform Disabled support for the CookieStore API due to compatibility concerns. The API will be enabled later once the compatibility issues have been addressed.</blockquote>
  14. 136.0.2 update and more settings changed again...

    136.0.2 update and more settings changed again...
  15. Heads up about MetaMask add-on causing website to break (related GH issue). See https://www.reddit.com/r/firefox/comments/1jevp4r/psa_disable_the_metamask_addon_if_you_have_it_and/ for more.

    Heads up about MetaMask add-on causing website to break (related [https://github.com/MetaMask/metamask-extension/issues/31094 GH issue]). See https://www.reddit.com/r/firefox/comments/1jevp4r/psa_disable_the_metamask_addon_if_you_have_it_and/ for more.
  16. Btw the MetaMask extension authors have a version 12.12.1 update as you can see at https://addons.mozilla.org/firefox/addon/ether-metamask/versions/

    Btw the MetaMask extension authors have a version 12.12.1 update as you can see at https://addons.mozilla.org/firefox/addon/ether-metamask/versions/
  17. Hi folks, please be aware that the team just released 136.0.3 today. I added that info to our wikipage as well.

    Hi folks, please be aware that the team just released [https://www.mozilla.org/firefox/136.0.3/releasenotes/ 136.0.3] today. I added that info to our [https://wiki.mozilla.org/Support/Firefox136 wikipage] as well.
  18. And a another (chemspill) update to Firefox 136.0.4 just got released: https://www.mozilla.org/en-US/security/advisories/mfsa2025-19/

    And a another (chemspill) update to Firefox 136.0.4 just got released: https://www.mozilla.org/en-US/security/advisories/mfsa2025-19/
  19. More specifically there were Firefox 136.0.4, 128.8.1esr and 115.21.1esr updates on March 27. https://www.mozilla.org/firefox/136.0.4/releasenotes/ https://www.mozilla.org/firefox/128.8.1/releasenotes/ https://www.mozilla.org/firefox/115.21.1/releasenotes/