Google has launched the release of the Chrome 101 web browser. At the same time, a stable release of the open-source project Chromium, which serves as the basis for Chrome, is available. The Chrome browser differs from Chromium by using Google logos, having a crash notification system, modules for playing copy-protected video content (DRM), an automatic update installation system, constant Sandbox isolation, provision of keys for Google APIs, and passing RLZ parameters during search. For those who need more time for updates, a separate Extended Stable branch is available, supported for 8 weeks, where an update for the previous Chrome 100 release has been created. The next release, Chrome 102, is scheduled for May 24. <\/p>\n
Key changes in Chrome 101: <\/p>\n
\n
The Side Search feature has been added, allowing users to view search results in a sidebar while simultaneously browsing another page (you can see both the page content and the search results in one window). After navigating from a Google search results page to another site, an icon with the letter «G» appears before the address input field; clicking it opens the sidebar with the results of the previous search. By default, this feature is not enabled on all systems; it can be enabled using the setting «chrome:\/\/flags\/#side-search».
<\/center>\n
Omnibox now features proactive prerendering of suggested content as you type. Previously, to speed up transitions from the address bar, the most likely suggestions were pre-fetched without waiting for the user to click, using a Prefetch call. Now, in addition to loading, they are also rendered in the buffer (including executing scripts and forming the DOM tree), ensuring instant display of recommendations upon clicking. To manage prerendering, the settings «chrome:\/\/flags\/#enable-prerender2», «chrome:\/\/flags\/#omnibox-trigger-for-prerender2», and «chrome:\/\/flags\/#search-suggestion-for-prerender2» are available.\n
Information in the HTTP header User-Agent and JavaScript parameters navigator.userAgent, navigator.appVersion, and navigator.platform has been trimmed. The header now only includes details about the browser name, major browser version (with MINOR.BUILD.PATCH version components replaced with 0.0.0), platform, and device type (mobile phone, PC, tablet). To obtain additional data, such as the exact version and extended platform data, the User Agent Client Hints API must be used. For sites that find this new information insufficient and are not yet ready to transition to User Agent Client Hints, the option to return the full User-Agent will be available until May 2023.\n
The behavior of the setTimeout function has changed when passing a zero argument defining the delay for the call. Starting with Chrome 101, specifying «setTimeout(…, 0)» will execute the code immediately, without the 1ms delay required by the specification. For repeated nested setTimeout calls, a 4 ms delay will be applied.\n
The Android platform version has implemented support for requesting notification permission (in Android 13, to display notifications, the app must have the «POST_NOTIFICATIONS» permission, without which notification sending will be blocked). When launching Chrome in an Android 13 environment, the browser will now prompt for notification permission.\n
The use of the WebSQL API in third-party scripts has been removed. By default, blocking WebSQL in scripts loaded from non-current sites was enabled in Chrome 97, but an option was provided to disable this behavior. In Chrome 101, that option has been removed. Further plans are to gradually discontinue support for WebSQL entirely, regardless of the context of use. It is recommended to use the Web Storage API and Indexed Database instead of WebSQL. The WebSQL handler is based on SQLite code and could have been exploited by attackers to take advantage of vulnerabilities in SQLite.\n
The names of enterprise policies (chrome:\/\/policy) containing non-inclusive terms have been removed. Starting with Chrome 86, replacements have been proposed for the specified policies, using inclusive terminology. Terms such as 'whitelist', 'blacklist', 'native', and 'master' have been cleaned up. For example, the policy URLBlacklist has been renamed to URLBlocklist, AutoplayWhitelist to AutoplayAllowlist, and NativePrinters to Printers.\n
The Origin Trials mode (experimental features requiring separate activation) has begun testing the Federated Credential Management API (FedCM) only in builds for the Android platform, allowing the creation of unified identification services that ensure privacy and operate without cross-site tracking mechanisms such as third-party cookie handling. The Origin Trial allows for interaction with the specified API from applications loaded from localhost or 127.0.0.1, or after registration and obtaining a special token valid for a limited time for a specific site.\n
A mechanism called Priority Hints has been stabilized and made available to all interested parties, allowing the importance of various loaded resources to be indicated by specifying an additional 'importance' attribute in tags such as iframe, img, and link. The attribute can take the values 'auto', 'low', and 'high', which affect the order in which the browser loads external resources.\n
The AudioContext.outputLatency property has been added, which provides information about the expected latency before sound output (the delay between the sound request and the start of processing the received data by the sound output device).\n
The CSS property font-palette and the @font-palette-values rule have been added, allowing the selection of a palette from a colored font or the definition of a custom palette. For example, this feature can be used to match colored symbolic fonts or emojis to the color scheme of content or to enable dark or light mode for the font.\n
The CSS function hwb() has been added, providing an alternative method for specifying colors in the sRGB format in HWB (Hue, Whiteness, Blackness), a format similar to HSL (Hue, Saturation, Lightness) but easier for human perception.\n
In the window.open() method, the specification of the popup property in the windowFeatures string, without assigning a value (i.e. when just popup is specified, not popup=true), is now processed as enabling the opening of a mini popup window (similar to 'popup=true') rather than defaulting to a value of 'false', which was illogical and misled developers.\n
The MediaCapabilities API, which provides information about the device and browser's abilities to decode multimedia content (supported codecs, profiles, bitrates, and resolutions), has added support for WebRTC streams.\n
The third version of the Secure Payment Confirmation API, which provides tools for additional confirmation of payment transactions, has been proposed. The new version includes support for identifiers that require input, icon determination for indicating verification failure, and an optional property payeeName.\n
The USBDevice API has added a forget() method to revoke previously granted user permissions for accessing the USB device. Additionally, instances of USBConfiguration, USBInterface, USBAlternateInterface, and USBEndpoint are now equal when strictly compared ('===' indicates one object) if they are returned for the same USBDevice object.\n
Improvements have been made to web developer tools. The ability to import and export user actions recorded in JSON format has been provided (example). In the web console and code inspection interface, the calculation and display of private properties have been enhanced. Support for the HWB color model has been added. The CSS panel now includes the ability to view cascading layers specified with the @layer rule.
<\/center> <\/ul>\n
In addition to new features and bug fixes, the new version resolves 30 vulnerabilities. Many of the vulnerabilities were identified through automated testing using tools such as AddressSanitizer, MemorySanitizer, Control Flow Integrity, LibFuzzer, and AFL. No critical issues were found that would allow bypassing all levels of browser protection and executing code on the system outside of the sandbox environment. As part of the bug bounty program for this release, Google has awarded 25 prizes totaling $81,000 (one prize of $10,000, three prizes of $7,500, three prizes of $7,000, one prize of $6,000, two prizes of $5,000, four prizes of $2,000, three prizes of $1,000, and one prize of $500). The amount of 6 prizes has yet to be determined. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Chrome](\"\/wp-content\/uploads\/2022\/04\/587c4733cde63b9032f1c4574470426f.jpg\")
<\/center>\n![\"Chrome](\"\/wp-content\/uploads\/2022\/04\/bd8155ae84fae1313a5f2194214ebfc2.jpg\")
<\/center> <\/ul>\n