The release of the web browser has taken place , as well as the mobile version for the Android platform. Additionally, an update has been created with long-term support and . Soon moving to the stage of the Firefox 80 branch will transition, with a release date set for August 25.
:
- The password manager has added the ability to export credentials in CSV format (text fields with delimiters, which can be imported into a spreadsheet). When exporting, passwords are placed in the file in plain text. There are also plans to implement a password import feature from a previously saved CSV file (it is assumed that users may need to back up and restore saved passwords or transfer passwords from another browser).
- setting to enable dynamic Cookie isolation based on the domain displayed in the address bar (, where own and third-party inserts are determined based on the site's base domain). The setting is offered in the configurator in the tracking protection settings section under the Cookie blocking methods dropdown.
- Enhanced tracking protection tools automatically block Cookies used by third-party counters. For tracking sites, Firefox now clears Cookies and data in internal storage daily, based on tracking system lists from Disconnect.me.
- A preliminary implementation of the experimental settings screen 'about:preferences#experimental' has been added, providing an interface to enable experimental features, similar to about:flags in Chrome. By default, the screen is currently unavailable and requires enabling the 'browser.preferences.experimental' setting in about:config. Currently, the only available experimental feature offered for activation is the support for«.
- For laptops based on AMD chips on the Windows 10 platform
the WebRender compositing system. WebRender is written in Rust and allows for significant increases in rendering speed and reduced CPU load by offloading rendering operations of page content to the GPU, which are implemented through shaders run on the GPU. Previously, WebRender was enabled on Windows 10 for Intel GPUs, AMD Raven Ridge APUs, AMD Evergreen chips, and laptops with NVIDIA graphics cards. On Linux, WebRender is still for Intel and AMD cards only in nightly builds, and not supported for NVIDIA cards. To force activation in about:config, you should enable the settings 'gfx.webrender.all' and 'gfx.webrender.enabled' or start Firefox with the environment variable MOZ_WEBRENDER=1. - For users in Germany, a new section has been added to the new tab page featuring articles recommended by the Pocket service, which had previously been offered to users in the USA and the UK. The content personalization related to recommendations is performed on the client side without transmitting user information to third parties (the entire list of recommended links for the current day, ranked based on browsing history, is loaded into the browser). A setting in the configurator (Firefox Home Content/Recommended by Pocket) and the option 'browser.newtabpage.activity-stream.feeds.topsites' in about:config is available to disable the recommended Pocket content.
- For Linux systems with Wayland due to stability issues by default, the use of the DMABUF mechanism for rendering video to textures. To enable it in about:config, the variable
'widget.wayland-dmabuf-video-textures.enabled' is provided. - A new button 'Clear Startup cache' has appeared on the about:support page to clear caches affecting browser startup. This button may help resolve some issues that occur during launch.
- Links with the target="_blank" attribute in tags <a> and <area> now similarly to using the rel="noopener" attribute, i.e., they are considered untrustworthy pages. For pages opened via these links, the Window.opener property is not set, and access to the context from which the link was opened is not granted.
- For iframes, the 'allow-top-navigation-by-user-activation' parameter has been implemented in the sandbox attribute, allowing navigation to the parent page from an isolated iframe upon an explicit user click on a link, but prohibiting automatic redirection. This option is useful for displaying banners in iframes, allowing transitions to the in-demand advertisement while blocking unwanted activities (such as automatic redirects to other pages).
- New HTTP headers have been added (COEP) and (COOP), allowing a special cross-origin isolation mode for the secure use of privileged operations on the page, which can be used to carry out attacks through side channels, such as Spectre.
- Support for the object (which allows creating arrays in shared memory), disabled after the detection of Spectre-class attacks. To ensure protection against Spectre, the SharedArrayBuffer object is now only available on pages processed in cross-origin isolation mode. In cross-origin isolation mode, non-truncated precision timers like Performance.now() are also now allowed.
To define such isolation, the aforementioned headers Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy should be used. - Implemented method , which returns the first fulfilled Promise from the list.
- The object for defining weak references to JavaScript objects, allowing to maintain a reference to an object without blocking the garbage collector from removing the associated object.
- New logical assignment operators have been added: “«, «" and "”. The “x ??= y” operator performs the assignment only if “x” is null or undefined. The “x ||= y” operator performs the assignment only if “x” is FALSE, while “x &&= y” assigns if it is TRUE.
- The object , used for organizing synchronization locks of primitives, can now be applied not only to shared memory.
- In the constructor support for dateStyle and timeStyle options has been added.
- WebAssembly has added support for (for more efficient modeling of memcpy and memmove operations), (Shared memory & Atomics) and (externref).
- In the JavaScript debugger, the stack , allowing the tracking of asynchronously executed events, timeouts, and promises. Chains of asynchronous calls are displayed in the debugger alongside the regular call stack, as well as shown for errors in the web console and requests in the network inspection interface.
- In the web console, the display of status codes 4xx/5xx as errors has been implemented, making them easier to highlight against the general background. For easier debugging, a request can be repeated or details about the request and response can be viewed.
- JavaScript errors are now displayed not only in the web console but also in the JavaScript debugger, highlighting the line of code associated with the error and showing a tooltip with additional information about the error.
- The reliability of opening source texts in SCSS and CSS-in-JS in the inspection interface has been improved. All panels have enhanced handling of mappings to the original source code based on the source map.
- A new Application panel has been added to the web developer tools, providing tools for inspecting and debugging service workers and web application manifests.
- The network inspection system has merged the Messages and Responses tabs.
- In Responsive Design Mode, touch gesture simulation with dragging and swiping using mouse movement is provided when touch screen simulation mode is enabled.
- will be the last release in this branch. In early August, users will be gradually transitioned to a new edition, under the code name Fenix and tested under the name Firefox Preview. Firefox 79 builds for Android will be based on the Fenix codebase. The new edition The GeckoView engine, built on Firefox Quantum technologies, and the set of libraries , which are already being used to build browsers and . GeckoView is a variant of the Gecko engine, packaged as a separate library that can be updated independently, while Android Components includes libraries with standard components that manage tab functionality, input autocompletion, search suggestions, and other browser capabilities. A minimum of Android 5.0 is required (support for Android 4.4.4 has been discontinued). Access to about:config is disabled by default.
In addition to new features and bug fixes, Firefox 79 15 of which are marked as critical. 12 vulnerabilities have been collected under ) are caused by memory handling issues, such as buffer overflows and dereferencing freed memory areas. These problems potentially allow an attacker to execute code when opening specially crafted pages.
Source: opennet.ru
