{"id":104770,"date":"2022-08-04T03:36:37","date_gmt":"2022-08-04T01:36:38","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-chrome-104"},"modified":"2022-08-04T03:36:37","modified_gmt":"2022-08-04T01:36:38","slug":"reliz-chrome-104","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-104","title":{"rendered":"Release of Chrome 104","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has released version 104 of the Chrome web browser. At the same time, a stable release of the open-source project Chromium, which forms the basis of Chrome, is also available. Chrome differs from Chromium in its use of Google logos, a notification system for crashes, modules for playing DRM-protected video content, an automatic update installation system, continuous Sandbox isolation, the provision of keys to Google APIs, and the transmission of RLZ parameters during searches. For those who need more time to update, the Extended Stable branch is supported separately, with an 8-week duration. The next release, Chrome 105, is scheduled for August 30. <\/p>\n
Key changes in Chrome 104: <\/p>\n
\n
A maximum lifespan for cookies has been introduced \u2014 all new or updated cookies will automatically be deleted after 400 days, even if the expiration time set through the Expires and Max-Age attributes exceeds 400 days (for such cookies, the lifespan will be cut down to 400 days). Cookies created before the introduction of this limit will maintain their lifespan, even if it exceeds 400 days, but will be limited upon updating. This change reflects new requirements noted in the draft of the new specification.\n
Blocking of requests from iframes to URLs that reference the local file system (\"filesystem:\/\/\") has been enabled.\n
A new optimization has been added to speed up page loading by establishing a connection to the target host at the moment a link is clicked, without waiting for the button to be released or the finger to be lifted from the touchscreen.\n
Settings have been added to manage the API \"Topics & Interest Group\", promoted under the Privacy Sandbox initiative, which allows defining user interest categories and using them instead of tracking cookies to highlight groups of users with similar interests without identifying individual users. Additionally, one-time informational dialogs have been added, explaining the technology to the user and offering to activate support in the settings.\n
Threshold values for limiting nested calls to setTimeout and setInterval timers, initiated with an interval of less than 4 ms (\"setTimeout(..., <4ms)") have been increased. The total limit for such calls has been raised from 5 to 100, which allows for aggressive non-limiting of individual calls, while still preventing abuses that could affect browser performance.\n
The sending of a CORS (Cross-Origin Resource Sharing) credential confirmation request to the main site's server has been enabled with the header \"Access-Control-Request-Private-Network: true\", in cases where a page requests a subresource in the internal network (192.168.x.x, 10.x.x.x, 172.16-31.x.x) or to localhost (127.x.x.x). Upon confirming the operation in response to this request, the server must return the header \"Access-Control-Allow-Private-Network: true\". In Chrome version 104, the result of the confirmation currently does not affect request handling\u2014if confirmation is absent, a warning is displayed in the web console, but the subresource request is not blocked. Blocking will be enabled in the absence of confirmation. server<\/a> expected no earlier than in the release of Chrome 107. To enable blocking in earlier releases, you can activate the setting «chrome:\/\/flags\/#private-network-access-respect-preflight-results».\n
![\"Release](\"\/wp-content\/uploads\/2022\/08\/c0a84e093eb2c23b3cd28d4f6a9b6402.jpg\")
<\/center> <\/ul>\n