The Firefox 111 web browser has been released. In addition, an update to the long-term support branch, 102.9.0, has been formed. The Firefox 112 branch, which is scheduled for release on April 11, will soon be transferred to the beta testing stage.
Key innovations in Firefox 111:
- Added the ability to create email address masks for the Firefox Relay service to the built-in account manager, which allows you to generate temporary email addresses for registering on sites or subscribing so as not to advertise your real address. The feature is only available when the user is connected to an account in Firefox Account.
- To tag added support for the “rel” attribute, which allows you to apply the “rel=noreferrer” parameter to navigation through web forms to disable the transfer of the Referer header or “rel=noopener” to disable setting the Window.opener property and deny access to the context from which the transition was made .
- The OPFS (Origin-Private FileSystem) API is enabled, which is an extension to the File System Access API for placing files in a local file system that are bound to the storage associated with the current site. A kind of virtual FS tied to the site is created (other sites cannot access it), which allows web applications to read, modify and save files and directories on the user's device.
- As part of the implementation of the CSS Color Level 4 specification, the color(), lab(), lch(), oklab(), and oklch() functions have been added to CSS to define colors in the sRGB, RGB, HSL, HWB, LHC, and LAB color spaces. The features are currently disabled by default and require the layout.css.more_color_4.enabled flag in about:config to be enabled.
- The CSS '@page' rules used to define the page when printing has a 'page-orientation' property to get the page orientation information ('upright', 'rotate-left' and 'rotate-right').
- In SVG inside elements the use of context-stroke and context-fill values is allowed.
- The search.query function has been added to the add-on API to send queries to the default search engine. Added a "disposition" property to the search.search function to display the search result in a new tab or window.
- Added an API for saving PDF documents opened in the built-in pdf.js viewer. Added the GeckoView Print API, which is related to window.print and allows you to send PDF files or a PDF InputStream for printing.
- Added support for setting permissions via SitePermissions for the file:// URI.
- Initial support for the RISC-V 64 architecture has been added to the SpiderMonkey JavaScript engine.
- Web developer tools allow searching in arbitrary files.
- Implemented support for copying surfaces for VA-API (Video Acceleration API) using dmabuf, which made it possible to speed up the processing of VA-API surfaces and solved problems with the appearance of artifacts during rendering on some platforms.
- Added network.dns.max_any_priority_threads and network.dns.max_high_priority_threads settings to about:config to control the number of threads used to resolve DNS hostnames.
- On the Windows platform, the use of the platform-provided system for displaying notifications is enabled.
- Session recovery is supported on the macOS platform.
- Improvements in Android version:
- The built-in ability to view PDF documents has been implemented (without the need for pre-loading and opening in a separate viewer).
- When you select the strict mode for blocking unwanted content (strict), the Cookie Protection mode (Total Cookie Protection) is enabled by default, in which a separate isolated cookie storage is used for each site, which does not allow the use of cookies to track movement between sites.
- Pixel devices running Android 12 and 13 now have the ability to send links to recently viewed pages directly from the Recents screen.
- The mechanism for opening content in a separate application (Open in app) has been redesigned. Addressed a vulnerability (CVE-2023-25749) that could allow third-party Android apps to run without user confirmation.
- A CanvasRenderThread handler has been included to handle WebGL related tasks on a separate thread.
In addition to innovations and bug fixes, 111 vulnerabilities have been fixed in Firefox 20. 14 vulnerabilities are marked as dangerous, of which 9 vulnerabilities (collected under CVE-2023-28176 and CVE-2023-28177) are caused by memory problems, such as buffer overflows and access to already freed memory areas. These issues can potentially lead to malicious code being executed when specially designed pages are opened.
Source: opennet.ru