Chrome Release 111

Google has unveiled the release of the Chrome 111 web browser. At the same time, a stable release of the free Chromium project, which is the basis of Chrome, is available. The Chrome browser differs from Chromium in the use of Google logos, the presence of a system for sending notifications in case of a crash, modules for playing copy-protected video content (DRM), an automatic update system, the constant inclusion of Sandbox isolation, the supply of keys to the Google API and transmission when searching for RLZ- parameters. For those who need more time to update, the Extended Stable branch is supported separately, followed by 8 weeks. The next release of Chrome 112 is scheduled for April 4th.

Key changes in Chrome 111:

  • Updated interface elements related to the Privacy Sandbox initiative to allow categories of user interests to be used instead of tracking cookies to highlight groups of users with similar interests without identifying individual users. The new version adds a new dialog that tells users about the Privacy Sandbox features and redirects them to a settings page where they can configure the information sent to ad networks.
    Chrome Release 111
    Chrome Release 111
  • A new dialog has been proposed with information about enabling the ability to synchronize settings, history, bookmarks, auto-completion databases and other data between browsers.
    Chrome Release 111
  • On Linux and Android platforms, name resolution operations in DNS are moved from an isolated network process to a non-isolated browser process, since when working with a system resolver, it is impossible to implement some sandbox restrictions that apply to other network services.
  • Added support for automatically signing in users to Microsoft identity services (Azure AD SSO) using account information from Microsoft Windows.
  • The Chrome update mechanism on Windows and macOS handles updates for the latest 12 versions of the browser.
  • Using the Payment Handler API, which simplifies integration with existing payment systems, now requires an explicit definition of the source of downloaded data by specifying the domains to which requests are sent in the connect-src (Content-Security-Policy) CSP parameter.
  • Removed the PPB_VideoDecoder(Dev) API, which was deprecated after Adobe Flash was discontinued.
  • The View Transitions API has been added to make it easier to create transitional animation effects between different DOM states (for example, a smooth transition from one image to another).
  • Support for the style() function has been added to the "@container" CSS query to apply styles depending on the computed values ​​of the parent element's custom properties.
  • The trigonometric functions sin(), cos(), tan(), asin(), acos(), atan() and atan2() have been added to CSS.
  • Added an experimental (origin trial) Document Picture in Picture API to open arbitrary HTML content in picture-in-picture mode, not just video. Unlike opening a window via the window.open() call, windows created via the new API are always displayed on top of other windows, do not remain after the original window is closed, do not support navigation, and cannot explicitly determine the position of the output.
    Chrome Release 111
  • Provided the ability to increase or decrease the size of the ArrayBuffer, as well as increase the size of the SharedArrayBuffer.
  • WebRTC implements support for SVC (Scalable Video Coding) extensions for adapting a video stream to the client's bandwidth and transmitting several video streams of different quality in one stream.
  • The "previousslide" and "nextslide" actions have been added to the Media Session API to organize navigation between the previous and next slides.
  • New ":nth-child(an + b)" and ":nth-last-child()" pseudo-class syntax has been added to allow getting a selector to pre-filter child elements before performing the main "An+B" selection logic on them.
  • CSS has added new units for the root element's font size: rex, rch, ric, and rlh.
  • Full support for the CSS Color Level 4 specification has been implemented, including support for seven color palettes (sRGB, RGB 98, Display p3, Rec2020, ProPhoto, CIE and HVS) and 12 color spaces (sRGB Linear, LCH, okLCH, LAB, okLAB, Display p3, Rec2020, a98 RGB, ProPhoto RGB, XYZ, XYZ d50, XYZ d65), in addition to previously supported Hex, RGB, HSL, and HWB colors. Provided the ability to use custom color spaces for animation and gradients.
  • CSS has added a new color() function that can be used to define a color in any color space in which colors are specified using the R, G, and B channels.
  • Added the color-mix() function, defined in the CSS Color 5 specification, which allows you to mix colors in any color space based on a given percentage (for example, to add 10% blue to white, you can specify "color-mix(in srgb, blue 10%, white);").
  • Improvements have been made to tools for web developers. Support for the CSS Color Level 4 specification and its new color spaces and palettes has been added to the Styles panel. Support for new color spaces and the ability to convert between different color formats has been added to the tool for determining the color of arbitrary pixels (β€œeyedropper”). The JavaScript debugger has a redesigned breakpoint control panel.
    Chrome Release 111

In addition to innovations and bug fixes, 40 vulnerabilities have been fixed in the new version. Many of the vulnerabilities were identified as a result of automated testing tools AddressSanitizer, MemorySanitizer, Control Flow Integrity, LibFuzzer and AFL. No critical issues that allow bypassing all browser protection levels and executing code in the system outside the sandbox environment have been identified. As part of the program for the payment of cash rewards for the discovery of vulnerabilities for the current release, Google paid 24 awards in the amount of 92 thousand US dollars (one award of $15000 and $4000, two awards of $10000 and $700, three awards of $5000, $2000 and $1000, five $3000 awards).

Source: opennet.ru

Add a comment