Web browser released , as well as mobile version for Android platform. In addition, an update has been long term support ΠΈ . Coming soon to the stage Firefox 80 branch will be switched, the release of which is scheduled for August 25th.
:
- Added the ability to export credentials in CSV format (delimited text fields that can be imported into a spreadsheet) in the password manager. When exporting, passwords are placed in the file in plaintext. In the future, it is also planned to implement the function of importing passwords from a previously saved CSV file (it is understood that the user may need to back up and restore saved passwords or transfer passwords from another browser).
- setting to enable dynamic cookie isolation for the domain displayed in the address bar (""when own and third-party inserts are determined based on the site's base domain). The setting is offered in the configurator in the movement tracking blocking settings section in the drop-down block of cookie blocking methods.
- Tracking protection has been improved to automatically block cookies used by third-party trackers. For tracking sites, Firefox now clears cookies and data in internal storage daily, based on lists of trackers from the Disconnect.me service.
- Added a preliminary implementation of the "about:preferences#experimental" experimental settings screen, which provides an interface for enabling experimental features, similar to about:flags in Chrome. By default, the screen is not yet available and requires setting "browser.preferences.experimental" in about:conifg to be enabled. Of the experimental features available for inclusion, only support is offered so far "Β«.
- For laptops based on AMD chips on the Windows 10 platform
WebRender compositing system. WebRender is written in Rust and allows you to achieve a significant increase in rendering speed and reduce CPU load by offloading page content rendering operations to the GPU side, which are implemented through GPU-executed shaders. WebRender was previously enabled on the Windows 10 platform for Intel GPUs, AMD Raven Ridge APUs, AMD Evergreen, and laptops with NVIDIA graphics cards. On Linux WebRender so far for Intel and AMD cards in nightly builds only, and is not supported for NVIDIA cards. To force enable in about:config, activate the "gfx.webrender.all" and "gfx.webrender.enabled" settings, or start Firefox with the MOZ_WEBRENDER=1 environment variable set. - For users in Germany, a new section has been added to the New Tab page with articles recommended by Pocket, which were previously offered for users in the US and UK. Personalization related to the selection of content is performed on the client side and without transferring user information to third parties (the entire list of recommended links for the current day is loaded into the browser, which is ranked on the user side, based on browsing history data). To disable recommended Pocket content, there is a setting in the configurator (Firefox Home Content/Recommended by Pocket) and the option "browser.newtabpage.activity-stream.feeds.topsites" in about:config.
- For Linux systems with Wayland due to stability issues by default, use the DMABUF mechanism for rendering video to textures. A variable is provided for inclusion in about:config
"widget.wayland-dmabuf-video-textures.enabled". - The about:support page has a new "Clear Startup cache" button to clear caches that affect browser loading. The button can help solve some startup problems.
- Links with target="_blank" attribute in tags and Now by analogy with using the rel="noopener" attribute, i.e. are perceived as untrustworthy pages. For pages opened by these links, the Window.opener property is not set and access to the context from which the link was opened is not opened.
- For iframes, the "allow-top-navigation-by-user-activation" parameter is implemented in the sandbox attribute, which allows navigation on the parent page from an isolated iframe when the user explicitly clicks on the link, but prohibits automatic redirection. This option is useful for placing banners in an iframe, allowing you to click through to ads of interest, but blocking unwanted activity (for example, automatic redirects to other pages).
- Added new HTTP headers (COEP) and (COOP) that allow you to enable a special cross-origin isolation mode for the secure use of privileged operations on the page that can be used to carry out attacks through third-party channels, such as Specter.
- Object support returned (allows creating arrays in shared memory), disabled after Specter class attacks were detected. To protect against Specter, the SharedArrayBuffer object is now only available on pages rendered in cross-origin isolation. In cross-origin isolation mode, it is also now allowed to use performance.now() timers that are not reduced in accuracy.
The aforementioned Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers should be used to define such isolation. - Method implemented , which returns the first fulfilled Promise from the list.
- Implemented object to define weak references (weak reference) to JavaScript objects, allowing you to save a reference to the object, but not blocking the removal of the associated object by the garbage collector.
- Added new logical assignment operators: "","" and "". The "x ??= y" operator performs an assignment only if "x" evaluates to null or undefined. The "x ||= y" operator performs an assignment only if "x" is FALSE and "x &&= y" is TRUE.
- Object , used to organize the synchronization of primitive locks, can now be applied not only to shared memory.
- To constructor added support for dateStyle and timeStyle options.
- Support added to WebAssembly (for more efficient simulation of memcpy and memmove), (Shared memory & Atomics) and (externalref).
- In the JavaScript debugger stack , which allows you to track asynchronously executed events, timeouts, and promises. Asynchronous call chains are displayed in the debugger along with the normal call stack, and are also listed for errors in the web console and requests in the network inspection interface.
- The web console provides the display of 4xx/5xx status codes in the form of errors, which makes it easier to distinguish them from the general background. To make debugging easier, the request can be retried, or details about the request and response can be viewed.
- JavaScript errors are now shown not only in the web console, but also in the JavaScript debugger, highlighting the line in the code associated with the error and showing a tooltip with additional information about the error.
- Improved reliability of opening SCSS and CSS-in-JS sources in the inspection interface. All panels have improved handling of comparisons with the original source code based on the source map.
- A new Application panel has been added to web developer tools to provide tools for inspecting and debugging service workers and web application manifests.
- The Network Inspection System combines the Messages and Responses tabs.
- Responsive Design Mode provides simulation of touch-and-drag and slide gestures using mouse movement when touch screen simulation is enabled.
- will be the last release in the branch. In early August, it is planned to gradually transfer users to the new edition, codenamed Fenix ββand tested under the name Firefox Preview. Firefox 79 builds for Android to the Fenix ββcodebase. New edition GeckoView engine built on Firefox Quantum technologies and a set of libraries , which are already used to build browsers ΠΈ . GeckoView is a variant of the Gecko engine that is packaged as a standalone library that can be updated independently, while Android Components includes libraries with generic components that provide tabs, input completion, search suggestions, and other browser features. Requires at least Android 5.0 to work (Android 4.4.4 has been discontinued). Access to about:config is disabled by default.
In addition to innovations and bug fixes in Firefox 79 , of which 15 are marked as dangerous. 12 vulnerabilities (collected under ) are caused by memory problems such as buffer overflows and accessing already freed memory areas. These issues can potentially lead to malicious code being executed when specially designed pages are opened.
Source: opennet.ru