SUMO community discussions

Firefox 41 Release Notes / Issues / Discussion

  1. Firefox 41 is scheduled for release on September 22nd, 2015


    Release Notes: https://www.mozilla.org/en-US/firefox/41.0/releasenotes/

    • Ability to set a profile picture for your Firefox Account
    • Firefox Hello now includes instant messaging
    • browser.newtab.url being removed due to abuse by malware
    • Lots of Windows 10 Bug Fixes
    • More Pocket Locales Rolling Out

    NEW Pocket Locales (this release): cs, es-MX, fr, hu, it, ko, nl, pl, pt-BR, pt-PT, ru, zh-CN, zh-TW

    All Locales which now come with Pocket: cs, de, en-GB, en-US, en-ZA, es-ES, es-MX, fr, hu, it, ja, ja-JP-mac, ko, nl, pl, pt-BR, pt-PT, ru, zh-CN, zh-TW

    Big (GOOD!) changes coming in Firefox 42! I will be talking more about these next week.

    Firefox 41 is scheduled for release on September 22nd, 2015 '''Release Notes:''' [https://www.mozilla.org/en-US/firefox/41.0/releasenotes/ https://www.mozilla.org/en-US/firefox/41.0/releasenotes/] * Ability to set a profile picture for your Firefox Account * Firefox Hello now includes instant messaging * browser.newtab.url being removed due to abuse by malware * Lots of Windows 10 Bug Fixes * More Pocket Locales Rolling Out ''NEW Pocket Locales (this release): cs, es-MX, fr, hu, it, ko, nl, pl, pt-BR, pt-PT, ru, zh-CN, zh-TW'' ''All Locales which now come with Pocket: cs, de, en-GB, en-US, en-ZA, es-ES, es-MX, fr, hu, it, ja, ja-JP-mac, ko, nl, pl, pt-BR, pt-PT, ru, zh-CN, zh-TW'' Big (GOOD!) changes coming in Firefox 42! I will be talking more about these next week.

    Modified by Mark Schmidt on

  2. For Firefox for Android there isn't too much in Firefox 41 for Android:

    release notes:

    For Firefox for Android there isn't too much in Firefox 41 for Android: * new search provider popup at the bottom of the screen https://support.mozilla.org/en-US/kb/use-awesome-screen-search-web-bookmarks-and-more#mobile::m41 * the beginning of multiple login support and revised password manager (starting in 41, much better in 42) https://support.mozilla.org/en-US/kb/copy-saved-password-firefox-android release notes: * https://www-dev.allizom.org/en-US/mobile/41.0/releasenotes/
  3. Mark Schmidt said

    • browser.newtab.url being removed due to abuse by malware

    Here's the add-on: New Tab Override

    ''Mark Schmidt [[#post-66815|said]]'' <blockquote> * browser.newtab.url being removed due to abuse by malware </blockquote> Here's the add-on: [https://addons.mozilla.org/en-US/firefox/addon/new-tab-override/ New Tab Override]
  4. norton's toolbar addons aren't compatible with 41 this time around and they are advising their users to switch browsers or downgrade/delay security updates :-/ https://community.norton.com/en/blogs/product-update-announcements/firefox-41-and-norton-toolbar-compatibility

    edit: and it looks like we were already moving back that change from ff40 to 41 for them in particular: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/B3H3j6FRVms/6DSn_GXbvTYJ

    norton's toolbar addons aren't compatible with 41 this time around and they are advising their users to switch browsers or downgrade/delay security updates :-/ https://community.norton.com/en/blogs/product-update-announcements/firefox-41-and-norton-toolbar-compatibility edit: and it looks like we were already moving back that change from ff40 to 41 for them in particular: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/B3H3j6FRVms/6DSn_GXbvTYJ

    Modified by philipp on

  5. philipp said

    norton's toolbar addons aren't compatible with 41 this time around <snip> and it looks like we were already moving back that change from ff40 to 41 for them in particular: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/B3H3j6FRVms/6DSn_GXbvTYJ

    Related bug: Bug 1179902 - Push deprecation of binary components to Firefox 41

    ''philipp [[#post-66842|said]]'' <blockquote> norton's toolbar addons aren't compatible with 41 this time around <snip> and it looks like we were already moving back that change from ff40 to 41 for them in particular: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/B3H3j6FRVms/6DSn_GXbvTYJ </blockquote> Related bug: ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1179902 Bug 1179902] - Push deprecation of binary components to Firefox 41''
  6. For New Tab Override, users may need to be reminded that the extension does not pick up the old browser.newtab.url preference value but needs to have the URL set on its Options page. For example:

    After installing the extension, you need to use its Options page to set the desired new tab page (instead of using about:config).

    Open the Add-ons page using either:

    * Ctrl+Shift+a (Mac: Cmd+Shift+a) * "3-bar" menu button (or Tools menu) > Add-ons

    In the left column, click Extensions. Then on the right side, find New Tab Override and click its Options button.

    Depending on the height of your screen, you may need to scroll down to enter the desired address into the form. For example:

    * ''Page thumbnails (default)'' => about:newtab * ''Blank tab'' => about:blank * ''Built-in Firefox home page'' => about:home * ''Any other page'' => full URL to the page

    Then tab or click away from that form field and you can test using Ctrl+t.

    Success?

    For New Tab Override, users may need to be reminded that the extension does not pick up the old browser.newtab.url preference value but needs to have the URL set on its Options page. For example: <code>After installing the extension, you need to use its Options page to set the desired new tab page (instead of using about:config). Open the Add-ons page using either: &#42; Ctrl+Shift+a (Mac: Cmd+Shift+a) &#42; "3-bar" menu button (or Tools menu) > Add-ons In the left column, click Extensions. Then on the right side, find New Tab Override and click its Options button. Depending on the height of your screen, you may need to scroll down to enter the desired address into the form. For example: &#42; &#39;&#39;Page thumbnails (default)&#39;&#39; => about:newtab &#42; &#39;&#39;Blank tab&#39;&#39; => about:blank &#42; &#39;&#39;Built-in Firefox home page&#39;&#39; => about:home &#42; &#39;&#39;Any other page&#39;&#39; => full URL to the page Then tab or click away from that form field and you can test using Ctrl+t. Success? </code>
  7. jscher2000 said

    For New Tab Override, users may need to be reminded that the extension does not pick up the old browser.newtab.url preference value but needs to have the URL set on its Options page. For example: After installing the extension, you need to use its Options page to set the desired new tab page (instead of using about:config).

    Or modify the extensions.newtaboverride@agenedia.com.url in about:config, same thing - different way :-)

    ''jscher2000 [[#post-66846|said]]'' <blockquote> For New Tab Override, users may need to be reminded that the extension does not pick up the old browser.newtab.url preference value but needs to have the URL set on its Options page. For example: <code>After installing the extension, you need to use its Options page to set the desired new tab page (instead of using about:config). </blockquote> Or modify the '''extensions.newtaboverride@agenedia.com.url''' in about:config, same thing - different way :-)
  8. firefox 41 on android does have a rather huge crashiness problem on certain devices: https://bugzilla.mozilla.org/show_bug.cgi?id=1207642

    firefox 41 on android does have a rather huge crashiness problem on certain devices: https://bugzilla.mozilla.org/show_bug.cgi?id=1207642
  9. philipp said

    norton's toolbar addons aren't compatible with 41 this time around and they are advising their users to switch browsers or downgrade/delay security updates :-/ https://community.norton.com/en/blogs/product-update-announcements/firefox-41-and-norton-toolbar-compatibility edit: and it looks like we were already moving back that change from ff40 to 41 for them in particular: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/B3H3j6FRVms/6DSn_GXbvTYJ

    Yes, we moved deprecating binary XPCOM from 40 to 41 at Norton's request.

    We'll be writing an article for this case, since some 1.4M users have the addon installed and enabled. The Norton article suggests using another browser or an outdated version of Firefox, which is ridiculous. Using an up to date Firefox is probably safer than using an out of date Firefox with the Norton toolbar.

    For users who use the "identity safe" feature to save their login information, the workaround is to use the Identity Safe screen from within the Norton product or simply open https://identitysafe.norton.com in a new tab.

    ''philipp [[#post-66842|said]]'' <blockquote> norton's toolbar addons aren't compatible with 41 this time around and they are advising their users to switch browsers or downgrade/delay security updates :-/ https://community.norton.com/en/blogs/product-update-announcements/firefox-41-and-norton-toolbar-compatibility edit: and it looks like we were already moving back that change from ff40 to 41 for them in particular: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/B3H3j6FRVms/6DSn_GXbvTYJ </blockquote> Yes, we moved deprecating binary XPCOM from 40 to 41 at Norton's request. We'll be writing an article for this case, since some 1.4M users have the addon installed and enabled. The Norton article suggests using another browser or an outdated version of Firefox, which is ridiculous. Using an up to date Firefox is probably safer than using an out of date Firefox with the Norton toolbar. For users who use the "identity safe" feature to save their login information, the workaround is to use the Identity Safe screen from within the Norton product or simply open https://identitysafe.norton.com in a new tab.
  10. "Warn me before closing " settings ? No more . how to set it if someone wants to do .

    "Warn me before closing " settings ? No more . how to set it if someone wants to do .
  11. there seems to be an increase in reports about "firefox not responding" issues (not sure if it's related to the firefox 41 or flash 19 update). some collected threads/bugs: https://etherpad.mozilla.org/Xr0JsCVN26

    there seems to be an increase in reports about "firefox not responding" issues (not sure if it's related to the firefox 41 or flash 19 update). some collected threads/bugs: https://etherpad.mozilla.org/Xr0JsCVN26
  12. Chandan_Baba said

    "Warn me before closing " settings ? No more . how to set it if someone wants to do .

    I don't use it myself, but would that be browser.showQuitWarning ?

    ''Chandan_Baba [[#post-66876|said]]'' <blockquote> "Warn me before closing " settings ? No more . how to set it if someone wants to do . </blockquote> I don't use it myself, but would that be '''browser.showQuitWarning''' ?
  13. philipp said

    there seems to be an increase in reports about "firefox not responding" issues (not sure if it's related to the firefox 41 or flash 19 update). some collected threads/bugs: https://etherpad.mozilla.org/Xr0JsCVN26

    Thank you so much for making this list, Philipp. It's definitely Flash 19 that is crashing. I just reproduced this bug myself using Firefox 40.0.3.

    Interestingly, the crash reporting functionality did not work. Neither did reloading the plugin. I had to completely close and re-open Firefox for anything Flash to work again.

    ''philipp [[#post-66878|said]]'' <blockquote> there seems to be an increase in reports about "firefox not responding" issues (not sure if it's related to the firefox 41 or flash 19 update). some collected threads/bugs: https://etherpad.mozilla.org/Xr0JsCVN26 </blockquote> Thank you so much for making this list, Philipp. It's definitely Flash 19 that is crashing. I just reproduced this bug myself using Firefox 40.0.3. Interestingly, the crash reporting functionality did not work. Neither did reloading the plugin. I had to completely close and re-open Firefox for anything Flash to work again.
  14. So FarmVille 2 is crashing in Chrome as well. It's an Adobe Flash 19 issue and not a browser issue. Adobe hasn't addressed it yet, but most likely will soon.

    Zynga actually reported the issue 2 days ago with regards to Chrome 45 (first Chrome bundled with Flash 19), but didn't actually offer any workaround/fix. https://www.zyngaplayersupport.com/article/farmville/Frequent-Shockwave-Flash-Player-crashes-en_US-1443017043486

    The ball is in Adobe's court on this one.

    So FarmVille 2 is crashing in Chrome as well. It's an Adobe Flash 19 issue and not a browser issue. Adobe hasn't addressed it yet, but most likely will soon. Zynga actually reported the issue 2 days ago with regards to Chrome 45 (first Chrome bundled with Flash 19), but didn't actually offer any workaround/fix. https://www.zyngaplayersupport.com/article/farmville/Frequent-Shockwave-Flash-Player-crashes-en_US-1443017043486 The ball is in Adobe's court on this one.
  15. Scribe said

    Chandan_Baba said
    "Warn me before closing " settings ? No more . how to set it if someone wants to do .

    I don't use it myself, but would that be browser.showQuitWarning ?

    Ah, Thanks Scribe. Btw do you know why new tab overrides "super starts extension settings" ? #AoAUserAsked

    ''Scribe [[#post-66879|said]]'' <blockquote> ''Chandan_Baba [[#post-66876|said]]'' <blockquote> "Warn me before closing " settings ? No more . how to set it if someone wants to do . </blockquote> I don't use it myself, but would that be '''browser.showQuitWarning''' ? </blockquote> Ah, Thanks Scribe. Btw do you know why new tab overrides "super starts extension settings" ? #AoAUserAsked
  16. We're working with Adobe's Flash team to fix the crash issue. What would really help right now is a more reliable way to reproduce it.

    So far the best way to reproduce the crash is to play FarmVille for a while. But that's not very reliable at all. So if anything comes up on the support forums, please post a link and/or instructions here!

    Thanks!

    We're working with Adobe's Flash team to fix the crash issue. What would really help right now is a more reliable way to reproduce it. So far the best way to reproduce the crash is to play FarmVille for a while. But that's not very reliable at all. So if anything comes up on the support forums, please post a link and/or instructions here! Thanks!
  17. Mark Schmidt said

    We're working with Adobe's Flash team to fix the crash issue. What would really help right now is a more reliable way to reproduce it. So far the best way to reproduce the crash is to play FarmVille for a while. But that's not very reliable at all. So if anything comes up on the support forums, please post a link and/or instructions here! Thanks!

    FF crashes every time I play Farmville 2. Doesn't usually take long. If FF would generate an error report you might be able to figure it out faster, however FF doesn't seem to be doing this. It completely locks up. Hope you and Adobe can figure this out soon.

    ''Mark Schmidt [[#post-66884|said]]'' <blockquote> We're working with Adobe's Flash team to fix the crash issue. What would really help right now is a more reliable way to reproduce it. So far the best way to reproduce the crash is to play FarmVille for a while. But that's not very reliable at all. So if anything comes up on the support forums, please post a link and/or instructions here! Thanks! </blockquote> FF crashes every time I play Farmville 2. Doesn't usually take long. If FF would generate an error report you might be able to figure it out faster, however FF doesn't seem to be doing this. It completely locks up. Hope you and Adobe can figure this out soon.
  18. MF9000 said

    FF crashes every time I play Farmville 2. Doesn't usually take long. If FF would generate an error report you might be able to figure it out faster, however FF doesn't seem to be doing this. It completely locks up. Hope you and Adobe can figure this out soon.

    When Firefox locks up it's called a hang, not a crash. Did you try disabling hardware acceleration in Flash settings? See my reply in the question you posted on the support forum, here: https://support.mozilla.org/en-US/questions/1085117#answer-786650

    ''MF9000 [[#post-66894|said]]'' <blockquote> FF crashes every time I play Farmville 2. Doesn't usually take long. If FF would generate an error report you might be able to figure it out faster, however FF doesn't seem to be doing this. It completely locks up. Hope you and Adobe can figure this out soon. </blockquote> When Firefox locks up it's called a hang, not a crash. Did you try disabling hardware acceleration in '''Flash settings'''? See my reply in the question you posted on the support forum, here: https://support.mozilla.org/en-US/questions/1085117#answer-786650
  19. there is a firefox version 41.0.1 in the making soon - it will notably contain some fixes for common crash issues:

    • bug 1178601 - this has gone trough the roof recently and is by far the topcrasher at the moment, it is suspected that some sort of code change on facbook triggered this among all channels. questions on sumo
    • bug 1207665 - persistent startup crash on devices with an intel gma 3150 graphics card
    • bug 1208008 - crash for users with the "Mozilla Archive Format" addon once they open some .maff or .mht files questions on sumo

    edit: and there is also talk about uplifting a patch for lots of the recent "firefox not responding" issues on our part at bug 1185639

    there is a firefox version 41.0.1 in the making soon - it will notably contain some fixes for common crash issues: * [https://bugzilla.mozilla.org/show_bug.cgi?id=1178601 bug 1178601] - this has gone trough the roof recently and is by far the topcrasher at the moment, it is suspected that some sort of code change on facbook triggered this among all channels. <sup>[https://support.mozilla.org/en-US/questions/all?tagged=bug1178601&show=all questions on sumo]</sup> * [https://bugzilla.mozilla.org/show_bug.cgi?id=1207665 bug 1207665] - persistent startup crash on devices with an intel gma 3150 graphics card * [https://bugzilla.mozilla.org/show_bug.cgi?id=1208008 bug 1208008] - crash for users with the "Mozilla Archive Format" addon once they open some .maff or .mht files <sup>[https://support.mozilla.org/en-US/questions/all?tagged=bug1208008&show=all questions on sumo]</sup> edit: and there is also talk about uplifting a patch for lots of the recent "firefox not responding" issues on our part at [https://bugzilla.mozilla.org/show_bug.cgi?id=1185639 bug 1185639]

    Modified by philipp on

  20. some more news about the hanging issue that spiked recently - in part it also seem to be due to firefox 41 (& flash 19). if you see users reporting that firefox 41 is not responding on sites with embedded flash content, that's probably this bug.

    i've tagged all questions that turned up in search which i presume to be about this issue with "bug1207766" and would be glad if anyone coming across new similar topics could do the same to get a better overview of the issue: https://support.mozilla.org/en-US/questions/firefox?tagged=bug1207766&show=all

    at the moments firefox devs are looking closer into the matter, but it looks like 42.0 shouldn't be affected, so upgrading might be one solution we can offer to affected users. in addition there will be a build2 for firefox 41.0.1 at https://archive.mozilla.org/pub/firefox/candidates/41.0.1-candidates/ soon which also contains a speculative fix for it. once it is available we might need to gather some quick feedback by affected users to tell us if this build fixes the issues and if so report that back to relman so that the update could be put live to the public (time is a bit of the essence).

    some more news about the hanging issue that spiked recently - in part it also seem to be due to firefox 41 (& flash 19). if you see users reporting that firefox 41 is not responding on sites with embedded flash content, that's probably this bug. i've tagged all questions that turned up in search which i presume to be about this issue with "[https://bugzilla.mozilla.org/show_bug.cgi?id=1207766 bug1207766]" and would be glad if anyone coming across new similar topics could do the same to get a better overview of the issue: https://support.mozilla.org/en-US/questions/firefox?tagged=bug1207766&show=all at the moments firefox devs are looking closer into the matter, but it looks like 42.0 shouldn't be affected, so upgrading might be one solution we can offer to affected users. in addition there will be a '''build2''' for firefox 41.0.1 at https://archive.mozilla.org/pub/firefox/candidates/41.0.1-candidates/ soon which also contains a speculative fix for it. once it is available we might need to gather some quick feedback by affected users to tell us if this build fixes the issues and if so report that back to relman so that the update could be put live to the public (time is a bit of the essence).
  1. 1
  2. 2