Mozilla released Firefox 80.0 on the Stable channel and Firefox ESR 78.2 / Firefox ESR 68.12 on the Extended Support Release channel on August 25, 2020. This version is a minor update.
Mozilla removes master password terminology to replace master password in Firefox 80
Like in a password manager, usernames and passwords for online services such as email accounts or online banking can be saved in Firefox. You in turn protect access to this data with a master password. With version 80, Mozilla did not technically modify this function, but gave it a different name.
Firefox removes browser terminology that has been identified as objectionable or exclusionary. We listen to the conversations taking place within the Mozilla community and the world at large, and pay attention when people tell us that certain terms we use in Firefox exclude and harm people.
“Master-slave” is a metaphor that perpetuates racism. Firefox craves inclusion and clarity; we don’t need terms derived from harmful metaphors when we have many more inclusive, more descriptive and non-racist alternatives. For this reason, all instances of Master Password are replaced by Primary Password in Firefox browsers and products.
The depreciation of the term master password also conforms to the “Drastic Language” section of the Mozilla Community Engagement Guidelines.
Block list of add-ons
Firefox 80 is the first version of the browser to include the new add-ons block list. Mozilla maintains a list of problematic browser extensions, such as malicious or privacy-damaging ones, that prevent add-ons included in Firefox from running. The main advantages of the new blocklist are that it significantly reduces the time it takes to load and analyze the blocklist.
The new block list mechanism is also introduced in Firefox ESR 78.x.
Add-ons allow users to add Firefox functionality for a personalized browsing experience. Most add-ons are created with the best intention, providing users with useful and enjoyable features. However, add-ons can also be used to compromise personal data and security.
When Mozilla becomes aware of add-ons that go against users’ expectations or otherwise put the privacy and security of users at risk, it takes action to prevent them from running in Firefox. This can happen proactively or in response to a report of abuse.
When Mozilla decides to prevent an add-on from running in Firefox, the publisher questions whether the risk is so great that it outweighs the user’s choice to install the software, the utility they provides, as well as the developer’s freedom to distribute and control their software. If Mozilla encounters a situation where it cannot make a clear decision, then it will look to the security side to protect the user.
Depending on the nature of the policy violation, Mozilla will use different types of blocking. With a hard block, the add-on is disabled in Firefox and users are not able to bypass the block. This action is reserved for additional modules with the following characteristics:
- They appear to be intentionally breaking policy;
- They contain critical security vulnerabilities;
- They compromise the confidentiality of users;
- They seriously bypass the user’s consent or control.
A light blocking will deactivate an add-on by default, but allow the user to replace it and continue using it. Such a block is used for additional modules with the following characteristics:
- They cause serious stability and performance issues in Firefox;
- They contain non-critical policy violations.
Add-ons that appear to be clones, repeats, or close copies of already blocked add-ons will also be removed. If a problem is known to affect only a subset of versions, the block can be applied specifically to the affected versions. Add-ons containing obscured or comparable illegible code will also be blocked.
Among the other changes:
- Firefox can be set as the default PDF reader for viewing PDF documents.
- The browser has a new preference for notifying users if a form is submitted from an unsecured to a secure context. The name is security.warn_submit_secure_to_insecure.
- Animations are reduced for users with reduced motion settings.
- Alt-Tab previews changed from 6 to 7.
- On the Enterprise side, the permissions policy has been updated to support virtual reality notifications.
- Firefox’s HTTPS-only mode is not exposed in Firefox 80 Stable settings.
Firefox pour Android
We can note this:
- AV1 and dav1d enabled by default on Android.
- The possibility of browsing several pages forwards or backwards after a long press.
- The ability to edit search suggestions before running searches.
- The possibility of activating the desktop mode for the sites in order to block the redirects towards the mobile pages.
- Highlighting an email address displays a new option to send an email to that address. Likewise, highlighting a phone number displays a new context menu option for making a call.
- Login information saved in Firefox for Android can now be edited.
- WebRender support for additional devices (with Adreno 6xx GPUs).
- The possibility to delete favorites by dragging them to the left or right.
Source : release note