SUMO community discussions

Firefox 48 Release Notes / Issues / Discussions

  • 33 Replies
  • Last reply by John99
  1. philipp
    philipp 1303 posts
    more options

    Firefox 48 is scheduled to be released on 2016-08-02

    release notes: https://www.mozilla.org/en-US/firefox/48.0/releasenotes/ fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox48 (to be disclosed at the time of release)

    ...and version 48 has a couple of things in store for us:

    • multiprocess firefox ('e10s') is starting to be rolled out: 1% of qualified users (no extensions, no rtl-locales, accessibility mode not switched on) will be moved to e10s (this is happening with the help of the "Multi-process staged rollout" a system addon) - https://asadotzler.com/2016/06/06/firefox-48-beta-release-and-e10s/
    • redesign of the urlbar dropdown: more results are shown & the dropdown fills the whole width of the browser now - bug 1181078
    • the download protection part of the safebrowsing feature will now also detect potentially unwanted software downloads (adware, browser hijackers) by default. this can be controlled through the browser.safebrowsing.downloads.remote.block_potentially_unwanted preference - bug 1265359
    • blocking of unnecessary flash content: some flash counting 'pixels', fingerprinting stuff etc will be blocked from loading to improve stability and page loading time. this is happening in the background without any user visible pref to control that - https://github.com/mozilla-services/shavar-plugin-blocklist

    on top of that some addon related changes:

    as always please feel free to add to the thread as other changes become known or in case there are particular trends in reported new problems on the forums :))

    Firefox 48 is scheduled to be released on 2016-08-02 release notes: https://www.mozilla.org/en-US/firefox/48.0/releasenotes/ fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox48 (to be disclosed at the time of release) ...and version 48 has a couple of things in store for us: * '''multiprocess firefox ('e10s') is starting to be rolled out''': 1% of qualified users (no extensions, no rtl-locales, accessibility mode not switched on) will be moved to e10s (this is happening with the help of the "Multi-process staged rollout" a system addon) - https://asadotzler.com/2016/06/06/firefox-48-beta-release-and-e10s/ * '''redesign of the urlbar dropdown''': more results are shown & the dropdown fills the whole width of the browser now - [https://bugzilla.mozilla.org/show_bug.cgi?id=1181078 bug 1181078] * the [https://wiki.mozilla.org/Security/Features/Application_Reputation_Design_Doc download protection part] of the safebrowsing feature will now also '''detect potentially unwanted software downloads''' (adware, browser hijackers) by default. this can be controlled through the ''browser.safebrowsing.downloads.remote.block_potentially_unwanted'' preference - [https://bugzilla.mozilla.org/show_bug.cgi?id=1265359 bug 1265359] * '''blocking of unnecessary flash content''': some flash counting 'pixels', fingerprinting stuff etc will be blocked from loading to improve stability and page loading time. this is happening in the background without any user visible pref to control that - https://github.com/mozilla-services/shavar-plugin-blocklist on top of that some addon related changes: * it looks like the '''enforcement of extension signing''' is finally put into action and the overwrite through the ''xpinstall.signatures.required'' pref will no longer be effective (no guarantees though, as this was postponed a couple of times already). affected users could switch to developer edition or nightly or use unbranded firefox builds. information on how to obtain them should be published at https://wiki.mozilla.org/Addons/Extension_Signing#FAQ by the time of the release. *'''redesign of the get addons discovery pane''' - https://blog.mozilla.org/addons/2016/07/18/a-better-add-on-discovery-experience/ *'''webextensions''' are here - https://blog.mozilla.org/addons/2016/04/29/webextensions-in-firefox-48/ as always please feel free to add to the thread as other changes become known or in case there are particular trends in reported new problems on the forums :))
  2. user633449
    user633449 503 posts
    more options

    Just an FYI, August 2nd is also the release date of the Windows 10 Anniversary Update, AFAIK there are no known issues with Firefox and the Windows 10 update, but as with any big Windows update you never know.

    Just an FYI, August 2nd is also the release date of the Windows 10 Anniversary Update, AFAIK there are no known issues with Firefox and the Windows 10 update, but as with any big Windows update you never know.
  3. jscher2000 - Support Volunteer
    jscher2000 - Support Volunteer 834 posts
    more options

    philipp said

    • redesign of the urlbar dropdown: more results are shown & the dropdown fills the whole width of the browser now - bug 1181078

    Now 10 results display by default instead of 12, but there's no scroll bar, so instead of seeing six and scrolling to another six, you now get to see the top 10 at once.

    The customary preference to show more results still should work (browser.urlbar.maxRichResults).

    The browser.urlbar.unifiedcomplete preference is obsoleted by the new design, so we should expect users to return and complain that it stopped working and curse us for that. Custom style rules can hide the top item (Visit example.com / Search someengine for blah), for example, I posted this one on userstyles.org:

    https://userstyles.org/styles/122394/url-bar-tweaks-remove-visit-search-scroll-bar

    ''philipp [[#post-69653|said]]'' <blockquote> * '''redesign of the urlbar dropdown''': more results are shown & the dropdown fills the whole width of the browser now - [https://bugzilla.mozilla.org/show_bug.cgi?id=1181078 bug 1181078] </blockquote> Now 10 results display by default instead of 12, but there's no scroll bar, so instead of seeing six and scrolling to another six, you now get to see the top 10 at once. The customary preference to show more results still should work (browser.urlbar.maxRichResults). The browser.urlbar.unifiedcomplete preference is obsoleted by the new design, so we should expect users to return and complain that it stopped working and curse us for that. Custom style rules can hide the top item (Visit example.com / Search someengine for blah), for example, I posted this one on userstyles.org: https://userstyles.org/styles/122394/url-bar-tweaks-remove-visit-search-scroll-bar

    Modified by jscher2000 - Support Volunteer on

  4. Paul
    Paul 1306 posts
    more options

    philipp said

    • blocking of unnecessary flash content: some flash counting 'pixels', fingerprinting stuff etc will be blocked from loading to improve stability and page loading time. this is happening in the background without any user visible pref to control that - https://github.com/mozilla-services/shavar-plugin-blocklist

    I do not disagree with this change at all, but given how much fun our favourite piece of Adobe software has given SUMO over the last couple of years (and further to this news story), will we have an article and/or common response to assist in explaining this to users?

    ''philipp [[#post-69653|said]]'' <blockquote> * '''blocking of unnecessary flash content''': some flash counting 'pixels', fingerprinting stuff etc will be blocked from loading to improve stability and page loading time. this is happening in the background without any user visible pref to control that - https://github.com/mozilla-services/shavar-plugin-blocklist </blockquote> I do not disagree with this change at all, but given how much fun our favourite piece of Adobe software has given SUMO over the last couple of years (and further to this [http://www.bbc.co.uk/news/technology-36856449 news story]), will we have an article and/or common response to assist in explaining this to users?
  5. Wesley Branton
    Wesley Branton 165 posts
    more options

    I've got a question related to the addon signing.

    When it was first implemented, there were tons of users asking how to get the addons back. Since the configuration boolean for addon signing will no longer be active, I am assuming that there will be no way to install unsigned addons on Firefox?

    I've got a question related to the addon signing. When it was first implemented, there were tons of users asking how to get the addons back. Since the configuration boolean for addon signing will no longer be active, I am assuming that there will be no way to install unsigned addons on Firefox?

    Modified by Wesley Branton on

  6. John99
    John99 3665 posts
    more options

    Not on the standard Release Builds AFAIK & presumably we are not going to encourage standard users to use unbranded or pre release versions.

    Not on the standard Release Builds AFAIK & presumably we are not going to encourage standard users to use unbranded or pre release versions.
  7. user633449
    user633449 503 posts
    more options

    I imagine if someone has already turned off the about:config pref to run an unsigned add-on, they will have the know how to use an unbranded build.

    I imagine if someone has already turned off the about:config pref to run an unsigned add-on, they will have the know how to use an unbranded build.
  8. Wesley Branton
    Wesley Branton 165 posts
    more options

    Tyler Downer said

    I imagine if someone has already turned off the about:config pref to run an unsigned add-on, they will have the know how to use an unbranded build.

    Not necessarily. There were lots of support threads opened regarding the add-on signing when it was first implemented, so many users were walked through step-by-step on how to allow unsigned add-ons on Firefox.

    When we disable that temporary work-around, those users that required assistance before will probably not have the knowledge to use an unbranded build.

    ''Tyler Downer [[#post-69667|said]]'' <blockquote>I imagine if someone has already turned off the about:config pref to run an unsigned add-on, they will have the know how to use an unbranded build. </blockquote> Not necessarily. There were lots of support threads opened regarding the add-on signing when it was first implemented, so many users were walked through step-by-step on how to allow unsigned add-ons on Firefox. When we disable that temporary work-around, those users that required assistance before will probably not have the knowledge to use an unbranded build.
  9. user633449
    user633449 503 posts
    more options

    An unbranded build will simply require downloading the exe, running it, and changing the pref again, not much more work. They will be able to find help here again if they need it.

    An unbranded build will simply require downloading the exe, running it, and changing the pref again, not much more work. They will be able to find help here again if they need it.
  10. ideato
    ideato 567 posts
    more options

    Tyler Downer said

    An unbranded build will simply require downloading the exe, running it, and changing the pref again, not much more work. They will be able to find help here again if they need it.

    https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds

    ''Tyler Downer [[#post-69669|said]]'' <blockquote> An unbranded build will simply require downloading the exe, running it, and changing the pref again, not much more work. They will be able to find help here again if they need it. </blockquote> https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds
  11. John99
    John99 3665 posts
    more options

    And note currently there is a glitch with unbranded builds either likely to upgrade to branded ones which defeats the of using them, or maybe not updating, in which case they are not secure.

    And note currently there is a glitch with unbranded builds either likely to upgrade to branded ones which defeats the of using them, or maybe not updating, in which case they are not secure. * [https://bugzilla.mozilla.org/show_bug.cgi?id=1290548 Bug 1290548 - Unbranded add-on developer builds are updating to branded Firefox builds]
  12. James
    James 1697 posts
    more options

    https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work#w_how-does-phishing-and-malware-protection-work-in-firefox

    https://blog.mozilla.org/security/2016/08/01/enhancing-download-protection-in-firefox/

    https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work#w_how-does-phishing-and-malware-protection-work-in-firefox https://blog.mozilla.org/security/2016/08/01/enhancing-download-protection-in-firefox/

    Modified by James on

  13. John99
    John99 3665 posts
    more options

    Yahoo Toolbar issues due to Yahoo changes from 1st August. These are likely to be blamed on the Fx48 upgrade.

    (James} https://downloads.yahoo.com/faqfirefoxtoolbar
    On August 1, 2016 we will simplify the Firefox Yahoo Toolbar and upgrade your browser to the New Tab by Yahoo extension experience. This extension provides a static version of Yahoo Toolbar and customizes your new tab page with Flickr photos and quick access to your top sites. Please note, you will no longer be able to modify your toolbar layout.

    Yahoo appears to have a simplified version of their toolbar extension at https://addons.mozilla.org/firefox/addon/yahoo-toolbar-and-new-tab/ and their https://toolbar.yahoo.com/ link leads to a more simple page.

    Yahoo Toolbar issues due to Yahoo changes from 1st August. These are likely to be blamed on the Fx48 upgrade. * [/questions/1133132 Where is my yahoo toolbar?] <blockquote> (James} https://downloads.yahoo.com/faqfirefoxtoolbar <blockquote>On August 1, 2016 we will simplify the Firefox Yahoo Toolbar and upgrade your browser to the New Tab by Yahoo extension experience. This extension provides a static version of Yahoo Toolbar and customizes your new tab page with Flickr photos and quick access to your top sites. Please note, you will no longer be able to modify your toolbar layout.</blockquote> Yahoo appears to have a simplified version of their toolbar extension at https://addons.mozilla.org/firefox/addon/yahoo-toolbar-and-new-tab/ and their https://toolbar.yahoo.com/ link leads to a more simple page.
  14. guigs
    guigs 769 posts
    more options

    philipp said

    ...and version 48 has a couple of things in store for us:

    Some extra details about FAQs that you might find with the rollout of e10s to a small amount of users.

    Q: Who will be in the initial rollout, and how were they selected? A: Beginning today, approximately 1% of Firefox users will get updated to multi-processing immediately. Users with extensions, A11y clients, RTL interfaces, and touchscreens will not be selected in the first round, nor will users running Windows XP.

    Q: How will this improve the browsing experience for Firefox users? A: The multi-process model offers many compelling advantages in responsiveness, stability and performance:

    • Responsiveness. By placing web content into a separate process from the browser interface, we can ensure that Firefox’s UI stays snappy even when a page is doing heavy computation or undergoing garbage collection.
    • Stability. Tabs shouldn’t crash, but when they do, isolating web content in separate processes means they can crash without taking down the rest of the browser. We can smartly restore the crashed tabs and mitigate most of the pain of a crash.
    • Performance. A multi-process architecture lets us spread work across the many CPU cores present in modern computers and smartphones, resulting in more efficient utilization of the underlying hardware.

    Q: My [name of addon] add-on just stopped working? Why?" A: Many, but not all, add-ons will require modification to work efficiently with this new design. You can see the compatibility status of popular add-ons at AreWeE10SYet.com, or use the compatibility checker to see what changes your add-on might need.

    Q: How can developers get help if an issue arises? A: Mozilla has early started to engage with Add-on developers to make the transition as smooth and convenient as possible. The Mozilla Developer Network also hosts extensive documentation on multi-process Firefox, including migration guides for add-on authors.

    ''philipp [[#post-69653|said]]'' <blockquote> ...and version 48 has a couple of things in store for us: * '''multiprocess firefox ('e10s') is starting to be rolled out''': 1% of qualified users (no extensions, no rtl-locales, accessibility mode not switched on) will be moved to e10s (this is happening with the help of the "Multi-process staged rollout" a system addon) - https://asadotzler.com/2016/06/06/firefox-48-beta-release-and-e10s/ </blockquote> Some extra details about FAQs that you might find with the rollout of e10s to a small amount of users. Q: Who will be in the initial rollout, and how were they selected? A: Beginning today, approximately 1% of Firefox users will get updated to multi-processing immediately. Users with extensions, A11y clients, RTL interfaces, and touchscreens will not be selected in the first round, nor will users running Windows XP. Q: How will this improve the browsing experience for Firefox users? A: The multi-process model offers many compelling advantages in responsiveness, stability and performance: * Responsiveness. By placing web content into a separate process from the browser interface, we can ensure that Firefox’s UI stays snappy even when a page is doing heavy computation or undergoing garbage collection. * Stability. Tabs shouldn’t crash, but when they do, isolating web content in separate processes means they can crash without taking down the rest of the browser. We can smartly restore the crashed tabs and mitigate most of the pain of a crash. * Performance. A multi-process architecture lets us spread work across the many CPU cores present in modern computers and smartphones, resulting in more efficient utilization of the underlying hardware. Q: My [name of addon] add-on just stopped working? Why?" A: Many, but not all, add-ons will require modification to work efficiently with this new design. You can see the compatibility status of popular add-ons at AreWeE10SYet.com, or use the compatibility checker to see what changes your add-on might need. Q: How can developers get help if an issue arises? A: Mozilla has early started to engage with Add-on developers to make the transition as smooth and convenient as possible. The Mozilla Developer Network also hosts extensive documentation on multi-process Firefox, including migration guides for add-on authors.
  15. jscher2000 - Support Volunteer
    jscher2000 - Support Volunteer 834 posts
    more options

    Probably many users of internal company sites have set up Firefox to automatically pass their Windows credentials for NTLM authentication.

    Firefox 48 no longer passes your Windows login automatically in private windows. If a user cannot get NTLM to work even in Safe Mode, it could be that they have automatic private browsing set (Safe Mode follows that preference). However, I suspect that would be the rare case.

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

    Probably many users of internal company sites have set up Firefox to automatically pass their Windows credentials for NTLM authentication. '''Firefox 48 no longer passes your Windows login automatically in private windows.''' If a user cannot get NTLM to work even in Safe Mode, it could be that they have automatic private browsing set (Safe Mode follows that preference). However, I suspect that would be the rare case. https://support.mozilla.org/questions/1134055
  16. guigs
    guigs 769 posts
    more options

    e10s is going out to 10% of users by the end of the week.

    e10s is going out to 10% of users by the end of the week.
  17. John99
    John99 3665 posts
    more options

    Note there is potentially still a bug or regression with tab behaviour in e10s

    I presume the 10% is only of those with no addons etc still so will be well below a real 10% of the user base.

    Note there is potentially still a bug or regression with tab behaviour in e10s * Ver. 48. Tab name doesn't update when moving tab to a new window. [/questions/1133951] I presume the 10% is only of those with no addons etc still so will be well below a real 10% of the user base.
  18. Chris Ilias
    Chris Ilias 2448 posts
    more options

    John99 said

    I presume the 10% is only of those with no addons etc still so will be well below a real 10% of the user base.

    You presume correct. :) It's bug 1292721.

    ''John99 [[#post-69825|said]]'' <blockquote> I presume the 10% is only of those with no addons etc still so will be well below a real 10% of the user base. </blockquote> You presume correct. :) It's bug 1292721.
  19. Wesley Branton
    Wesley Branton 165 posts
    more options

    I've got a question: does anyone know when the developers will give web extensions the ability to display an icon in the context menu?

    The MDN documentation says that it was added in Firefox 47.0 but it doesn't work. I can't get it to work in 48.0 or 49.0, but I can get it to work in 52.0.

    Is this something that the developers just forgot to push through to the release or is there some reason that they are not adding it?

    I've got a question: does anyone know when the developers will give web extensions the ability to display an icon in the context menu? The MDN documentation says that it was added in Firefox 47.0 but it doesn't work. I can't get it to work in 48.0 or 49.0, but I can get it to work in 52.0. Is this something that the developers just forgot to push through to the release or is there some reason that they are not adding it?
  20. philipp
    philipp 1303 posts
    more options

    hi wesley, the best place for addon development related questions is https://discourse.mozilla-community.org/c/add-ons/development as the addon team members will read along and reply there regularly...

    hi wesley, the best place for addon development related questions is https://discourse.mozilla-community.org/c/add-ons/development as the addon team members will read along and reply there regularly...
  1. 1
  2. 2