{"id":104987,"date":"2022-09-01T21:36:44","date_gmt":"2022-09-01T19:36:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-chrome-105"},"modified":"2022-09-01T21:36:44","modified_gmt":"2022-09-01T19:36:45","slug":"reliz-chrome-105","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-105","title":{"rendered":"Release of Chrome 105","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has released version 105 of the Chrome web browser. At the same time, there is a stable release of the open-source project Chromium, which serves as the basis for Chrome. The Chrome browser differs from Chromium in its use of Google logos, a system for sending crash notifications, modules for playing protected video content (DRM), automatic update installation, always-on Sandbox isolation, provision of keys for Google API, and transmission of RLZ parameters during searches. For those needing more time to update, an Extended Stable branch is separately maintained, lasting for 8 weeks. The next release of Chrome 106 is scheduled for September 27. <\/p>\n
Key changes in Chrome 105: <\/p>\n
\n
Support for specialized web applications, Chrome Apps, has been discontinued, and they have been replaced by standalone web applications based on Progressive Web Apps (PWA) technology and standard Web APIs. Initially, Google announced its intention to discontinue Chrome Apps back in 2016 and planned to cease support by 2018, but this plan was later postponed. In Chrome 105, a warning about the discontinuation of support for Chrome Apps will be displayed when attempting to install them, but the applications will still continue to run. In Chrome 109, the execution of Chrome Apps will be disabled.\n
Additional isolation has been ensured for the «renderer» process responsible for rendering. This process now runs in an additional container (App Container) implemented above the existing sandbox isolation system. In the event of exploitation of a vulnerability in the rendering code, the added restrictions will prevent an attacker from accessing the network by prohibiting system calls related to network capabilities.\n
A unified storage system for root certificates from certificate authorities (Chrome Root Store) has been implemented. This new storage is not yet enabled by default, and until the implementation is completed, certificates will continue to be verified using the storage specific to each operating system. The tested solution resembles Mozilla's approach, which maintains a separate independent storage of root certificates for Firefox, used as the first link in the trust chain verification of certificates when opening websites via HTTPS.\n
Preparation has begun for the discontinuation of the Web SQL API, which is non-standard, rarely used, and requires a complete overhaul to meet modern security requirements. In Chrome 105, access to Web SQL from code loaded without HTTPS is prohibited, and a deprecation warning has been added in DevTools. The Web SQL API is planned for removal in 2023. An alternative based on WebAssembly will be prepared for developers who need similar functionality.\n
In Chrome, sync support has been discontinued for Chrome 73 and earlier versions.\n
A built-in certificate viewer has been activated for macOS and Windows platforms, replacing the operating system's interface call. Previously, the built-in viewer was only used in builds for Linux and ChromeOS.\n
The Android platform version has added settings to manage the «Topics & Interest Group» API, promoted under the Privacy Sandbox initiative, which allows defining user interest categories and using them instead of tracking cookies to group users with similar interests without identifying individual users. In the previous release, similar settings were added to the versions for Linux, ChromeOS, macOS, and Windows.\n
When enhanced browser protection (Safe Browsing > Enhanced protection) is enabled, telemetry collection regarding installed extensions, API calls, and connections to external sites is implemented. This data is used on Google servers to detect malicious activity and violations by browser extensions.\n
The ability to use non-ASCII characters in domains specified in the Cookie header has been moved to the deprecated category and will be blocked in Chrome 106 (for IDN domains, domains should be specified in punycode format). This change will align the browser with the requirements of RFC 6265bis and the behavior implemented in Firefox.\n
The Custom Highlight API allows for arbitrary styling of highlighted text areas, enabling flexibility beyond the fixed styles provided by the browser (such as ::selection and ::inactive-selection) and the highlighting of syntax errors (like ::spelling-error and ::grammar-error). The initial version of the API supports changing text and background colors using the color and background-color pseudo-elements, with additional styling capabilities planned for future updates.\n
Examples of tasks that can be addressed with the new API include integrating custom text highlighting mechanisms into web frameworks that provide text editing tools, varied highlighting during simultaneous collaboration by multiple users, searching in virtualized documents, and marking errors during spell checking. Previously, creating non-standard highlighting required complex manipulations of the DOM tree, but the Custom Highlight API offers ready-to-use operations for adding and removing highlights without affecting the DOM structure and applying styles tied to Range objects. <\/p>\n
A «@container» query has been added to CSS, allowing the styling of elements based on the size of their parent element. «@container» is similar to «@media» queries, but it applies not to the size of the entire visible area but to the size of the block (container) in which the element is placed, enabling the specification of custom style selection logic for child elements that is independent of the element's placement on the page.
<\/center>\n
The CSS pseudo-class ":has()" has been added to check for the presence of a child element within a parent. For example, "p:has(span)" targets elements <p>, which contain an element <span>.\n
The HTML Sanitizer API has been added, which allows for the removal of elements from content that affect display and execution when outputting via the setHTML() method. This API is useful for cleaning incoming external data by stripping out HTML tags that could be used for XSS attacks.\n
The Streams API (ReadableStream) can now be utilized to send fetch requests before the body of the response has loaded, meaning that data can begin to be sent without waiting for the page generation to finish.\n
For standalone web applications (PWA, Progressive Web App), the ability to customize the appearance of the window title area is provided through Window Controls Overlay components, which extend the screen area of the web application to the entire window, giving the web application the look of a regular desktop application. The web application can manage rendering and input handling across the entire window, except for the overlaid block with standard window control buttons (close, minimize, maximize).
<\/center>\n
The ability to access Media Source Extensions from dedicated workers (in the context of DedicatedWorker) has been stabilized. This can be used, for example, to enhance the performance of buffered multimedia playback by creating a MediaSource object in a separate worker and streaming the results to an HTMLMediaElement in the main thread.\n
![\"Release](\"\/wp-content\/uploads\/2022\/09\/675b361c92314f60ecd5fad332370546.jpg\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2022\/09\/393e1dbf845ba2199c94b24fc95618a7.jpg\")
<\/center>\n