SUMO community discussions

Firefox 40 (beta) Release Notes / Issues / Discussion

  1. Firefox 40.0.2 is now the current. www.mozilla.org/firefox/all https://www.mozilla.org/firefox/40.0.2/releasenotes/
  2. I am disappointed Firefox's new magical cyberwar powersbug1150180 will not work for me. So I filed bug 1194494


    ideato said

    Hey  :-) we don't have a separate section for 40 ...stable now ? https://www.mozilla.org/en-US/firefox/40.0/releasenotes/
    -) :-)
    We do now /firefox/40.0/releasenotes/, but I note that includes
    User can receive suggested tiles in the new tab page based on categories Firefox matches to browsing history (en-US only).

    However looking at

    Where/what countries are suggested sites being served? Enhanced and Directory sites are currently available in the following localized versions of Firefox: English, German, Spanish, Japanese, Polish, Portuguese and Russian. More versions will be released over time.

    We have a discrepancy over which locales are affected.

    I am disappointed Firefox's new magical cyberwar powers<sup>[https://bugzilla.mozilla.org/show_bug.cgi?id=1150180 bug1150180]</sup> will not work for me. So I filed bug [https://bugzilla.mozilla.org/show_bug.cgi?id=1194494 1194494] ''ideato [[#post-66402|said]]'' <blockquote> Hey :-) we don't have a separate section for 40 ...stable now ? https://www.mozilla.org/en-US/firefox/40.0/releasenotes/ :-) :-) </blockquote> We do now [/firefox/40.0/releasenotes/], but I note that includes <blockquote>User can receive [https://www.mozilla.org/firefox/tiles/ suggested tiles] in the new tab page based on categories Firefox matches to browsing history (en-US only).</blockquote> However looking at <blockquote>Where/what countries are suggested sites being served? Enhanced and Directory sites are currently available in the following localized versions of Firefox: English, German, Spanish, Japanese, Polish, Portuguese and Russian. More versions will be released over time.</blockquote> We have a discrepancy over which locales are affected.
  3. Extensions which use the old widgets module are failing in Firefox 40. These include:

    And another one:

    And a fourth one:

    Extensions which use the old widgets module are failing in Firefox 40. These include: * 1Password version 3 (older version) ** Publisher suggests upgrading or using ESR: https://support.1password.com/v3-extension-firefox/ ** Forum responses implied they might give free upgrades if you contact them directly ** https://support.mozilla.org/questions/1077494 * Skype Click to Call (current version) ** It's hackable: https://support.mozilla.org/questions/1077493#answer-767133 And another one: * PasswordBox (current release from [https://www.passwordbox.com/]) ** No support information from Intel/McAfee that I can find ** https://support.mozilla.org/questions/1077869#answer-767323 And a fourth one:<br> * [https://addons.mozilla.org/firefox/addon/translator/ translator from AMO] ** I created an issue on the extension's Github: https://github.com/badams/translator-firefox-addon/issues/8 ** A new version has been submitted to AMO and is pending review: https://addons.mozilla.org/firefox/addon/translator/versions/ ** https://support.mozilla.org/questions/1078319

    Modified by jscher2000 - Support Volunteer on

  4. I am seeing a high number of startup crashes questions, in this case the browser will not open in safe mode either. Some of the cases for this is due to Bug 1181091 however, without actual crash report IDs and knowing what the user has installed, it isn't possible to run this out in all cases for crashes. If these crashes are a result due to this bug, the current culprit for this seems to be Websense Endpoint. In cases where this is the issue, users will be posting their issue from a different browser where the information about their browser will be limited.

    I am seeing a high number of startup crashes questions, in this case the browser will not open in safe mode either. Some of the cases for this is due to [https://bugzilla.mozilla.org/show_bug.cgi?id=1181091 Bug 1181091] however, without actual crash report IDs and knowing what the user has installed, it isn't possible to run this out in all cases for crashes. If these crashes are a result due to this bug, the current culprit for this seems to be Websense Endpoint. In cases where this is the issue, users will be posting their issue from a different browser where the information about their browser will be limited.
  5. Also, are we forcing mobile versions of webpages for users on Windows 10? https://support.mozilla.org/en-US/questions/1077804

    Also, are we forcing mobile versions of webpages for users on Windows 10? https://support.mozilla.org/en-US/questions/1077804
  6. Andrew said

    Also, are we forcing mobile versions of webpages for users on Windows 10? https://support.mozilla.org/en-US/questions/1077804

    I get mobile for those on Windows 7, too, so I don't think it's a Windows 10 issue. I added a comment in the thread that at least there is a full site link at the bottom of those pages to work around it.

    ''Andrew [[#post-66455|said]]'' <blockquote> Also, are we forcing mobile versions of webpages for users on Windows 10? https://support.mozilla.org/en-US/questions/1077804 </blockquote> I get mobile for those on Windows 7, too, so I don't think it's a Windows 10 issue. I added a comment in the thread that at least there is a full site link at the bottom of those pages to work around it.
  7. there will be a 40.0.3 update released in the coming days, with fixes for two crashes (linux and startupcrash with old displaylink drivers), web compatibility and three vulnerabilities.

    https://wiki.mozilla.org/Firefox/Channels/Meetings/2015-08-25

    there will be a 40.0.3 update released in the coming days, with fixes for two crashes (linux and startupcrash with old displaylink drivers), web compatibility and three vulnerabilities. https://wiki.mozilla.org/Firefox/Channels/Meetings/2015-08-25
  8. https://developer.mozilla.org/en-US/Firefox/Releases/40/Site_Compatibility lists some of the issues that will be "fixed with Firefox 40.0.3", including: Bug 1198590 - Disable dom.ipc.plugins.asyncInit in Firefox 40 and 41 Beta ... which came up in /questions/1078397

    https://developer.mozilla.org/en-US/Firefox/Releases/40/Site_Compatibility lists some of the issues that will be "fixed with Firefox 40.0.3", including: [https://bugzilla.mozilla.org/show_bug.cgi?id=1198590 Bug 1198590] - Disable dom.ipc.plugins.asyncInit in Firefox 40 and 41 Beta ... which came up in [/questions/1078397]
  9. 40.0.3 is now deployed via auto-update https://www.mozilla.org/en-US/firefox/40.0.3/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-95/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-94/
  10. looks like 64bit for windows isn't necessarily shipping in 41 after all: https://bugzilla.mozilla.org/show_bug.cgi?id=1185532#c14

    looks like 64bit for windows isn't necessarily shipping in 41 after all: https://bugzilla.mozilla.org/show_bug.cgi?id=1185532#c14
  11. Bug 1200027 - 40.0.3 broke ability to install featured addons from the add-ons manager

    [https://bugzilla.mozilla.org/show_bug.cgi?id=1200027 Bug 1200027] - 40.0.3 broke ability to install featured addons from the add-ons manager
  12. philipp said

    looks like 64bit for windows isn't necessarily shipping in 41 after all: https://bugzilla.mozilla.org/show_bug.cgi?id=1185532#c14

    See bug 1181014 comment 12. The release target for Win64 builds was moved to Firefox 42.

    ''philipp [[#post-66600|said]]'' <blockquote> looks like 64bit for windows isn't necessarily shipping in 41 after all: https://bugzilla.mozilla.org/show_bug.cgi?id=1185532#c14 </blockquote> See [https://bugzilla.mozilla.org/show_bug.cgi?id=1181014#c12 bug 1181014 comment 12]. The release target for Win64 builds was moved to Firefox 42.
  13. Excuse me, is there a discussion about articles updates for the next release (Firefox 41)? I don't manage to find it.

    Thanks.

    Excuse me, is there a discussion about articles updates for the next release (Firefox 41)? I don't manage to find it. Thanks.
  14. I've just brought this to the community meeting today, it seems nothing is up yet. Joni is on holidays she will gives us an update when she comes back Wednesday.

    I've just brought this to the community meeting today, it seems nothing is up yet. Joni is on holidays she will gives us an update when she comes back Wednesday.
  15. Hi Underpass,

    We don't have an overarching discussion thread for version 41 article updates, but we've been tracking them in this spreadsheet as well as adding them to the "needs update" column in the KB dashboard. They are both kept up to date.

    Version 41 is pretty light, so we're actually done with the updates for now. The only major update was instant messaging for Firefox Hello, but you or Michele already localized the article a few weeks ago.

    Let me know if you'd like a different way of keeping track of article updates.

    Thanks! Joni

    Hi Underpass, We don't have an overarching discussion thread for version 41 article updates, but we've been tracking them [https://docs.google.com/spreadsheets/d/1lkpRPJp9P1P5MRU-c9dwbDC0w5bMmrMdu-BNMp1xe8w/edit#gid=6 in this spreadsheet] as well as adding them to the "needs update" column in the [https://support.mozilla.org/en-US/contributors KB dashboard]. They are both kept up to date. Version 41 is pretty light, so we're actually done with the updates for now. The only major update was instant messaging for Firefox Hello, but you or Michele already localized the article a few weeks ago. Let me know if you'd like a different way of keeping track of article updates. Thanks! Joni
  16. Um, what about this? I think it will generate a lot of (upset) posts.

    The browser.newtab.url preference is abused and should be removed https://bugzilla.mozilla.org/show_bug.cgi?id=1118285

    One known workaround: https://addons.mozilla.org/firefox/addon/new-tab-override/

    Edit: The preference was hidden from this article, so it is up to date as far as it goes: Customize items on your Firefox New Tab page. Since we are in the realm of unsupported options, perhaps a replacement for the ability to modify browser.newtab.url is more a "canned answer" issue than a KB issue.

    Um, what about this? I think it will generate a lot of (upset) posts. '''The browser.newtab.url preference is abused and should be removed''' https://bugzilla.mozilla.org/show_bug.cgi?id=1118285 One known workaround: https://addons.mozilla.org/firefox/addon/new-tab-override/ ''Edit: The preference was hidden from this article, so it is up to date as far as it goes:'' [[Hide or display Tiles in New Tab]]. ''Since we are in the realm of unsupported options, perhaps a replacement for the ability to modify'' browser.newtab.url ''is more a "canned answer" issue than a KB issue.''

    Modified by jscher2000 - Support Volunteer on

  17. according to https://bugzilla.mozilla.org/show_bug.cgi?id=1203584 there is now a new timetable for enforcing addon signing:

    • users will be warned about unsigned addons starting from firefox 40 to 42
    • only accepting signed addons will be the default setting starting in firefox 43
    • addon signing will be enforced with no pref to disable it in firefox 44
    according to https://bugzilla.mozilla.org/show_bug.cgi?id=1203584 there is now a new timetable for enforcing addon signing: * users will be warned about unsigned addons starting from firefox 40 to 42 * only accepting signed addons will be the default setting starting in firefox 43 * addon signing will be enforced with no pref to disable it in firefox 44
  18. https://wiki.mozilla.org/Addons/Extension_Signing Firefox 40-42: Firefox warns about signatures but doesn't enforce them. Firefox 43: Firefox will have a preference that allows signature enforcement to be disabled (xpinstall.signatures.required in about:config). Firefox 44: Release and Beta versions of Firefox 44 will not allow unsigned extensions to be installed, with no override.

    Which add-on types will need to be signed? Only Extensions as Themes, dictionaries, language packs, and Plugins don't need to be signed.


    As the word Addons does not equal Extensions only.

    https://wiki.mozilla.org/Addons/Extension_Signing Firefox 40-42: Firefox warns about signatures but doesn't enforce them. Firefox 43: Firefox will have a preference that allows signature enforcement to be disabled (xpinstall.signatures.required in about:config). Firefox 44: Release and Beta versions of Firefox 44 will not allow unsigned extensions to be installed, with no override. Which add-on types will need to be signed? Only '''Extensions''' as Themes, dictionaries, language packs, and Plugins don't need to be signed. As the word Addons does not equal Extensions only.
  19. language packs will be required to be signed as well (bug 1197876)

    language packs will be required to be signed as well ([https://bugzilla.mozilla.org/show_bug.cgi?id=1197876 bug 1197876])
  20. jscher2000 said

    Um, what about this? I think it will generate a lot of (upset) posts. The browser.newtab.url preference is abused and should be removed https://bugzilla.mozilla.org/show_bug.cgi?id=1118285 One known workaround: https://addons.mozilla.org/firefox/addon/new-tab-override/ Edit: The preference was hidden from this article, so it is up to date as far as it goes: Customize items on your Firefox New Tab page. Since we are in the realm of unsupported options, perhaps a replacement for the ability to modify browser.newtab.url is more a "canned answer" issue than a KB issue.

    Does anyone know if the SearchReset add-on - https://addons.mozilla.org/en-US/firefox/addon/searchreset/ will be broken by the browser.newtab.url changes in FF 41, or will the home page and search reset part of it still work? It is linked to in at least one KB - https://support.mozilla.org/en-US/kb/remove-toolbar-has-taken-over-your-firefox-search

    ''jscher2000 [[#post-66711|said]]'' <blockquote> Um, what about this? I think it will generate a lot of (upset) posts. '''The browser.newtab.url preference is abused and should be removed''' https://bugzilla.mozilla.org/show_bug.cgi?id=1118285 One known workaround: https://addons.mozilla.org/firefox/addon/new-tab-override/ ''Edit: The preference was hidden from this article, so it is up to date as far as it goes:'' [[Hide or display Tiles in New Tab]]. ''Since we are in the realm of unsupported options, perhaps a replacement for the ability to modify'' browser.newtab.url ''is more a "canned answer" issue than a KB issue.'' </blockquote> Does anyone know if the SearchReset add-on - https://addons.mozilla.org/en-US/firefox/addon/searchreset/ will be broken by the browser.newtab.url changes in FF 41, or will the home page and search reset part of it still work? It is linked to in at least one KB - https://support.mozilla.org/en-US/kb/remove-toolbar-has-taken-over-your-firefox-search
  1. 1
  2. 2