{"id":120236,"date":"2024-10-21T13:09:17","date_gmt":"2024-10-21T11:09:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-web-brauzera-chrome-130"},"modified":"2024-10-21T13:09:17","modified_gmt":"2024-10-21T11:09:20","slug":"vypusk-web-brauzera-chrome-130","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-web-brauzera-chrome-130","title":{"rendered":"Release of web browser Chrome 130","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has released version 130 of the Chrome web browser. At the same time, the stable release of the free project Chromium, which underpins Chrome, is available. Chrome differs from Chromium in its use of Google logos, a crash notification system, modules for playing protected video content (DRM), an automatic update installation system, constant Sandbox isolation, provision of keys to Google API, and the transmission of RLZ parameters during searches. For those who need more time to update, an Extended Stable branch is maintained, which is supported for 8 weeks. The next release of Chrome 131 is scheduled for November 12. <\/p>\n
Key changes in Chrome 130: <\/p>\n
\n
A new form of compact notifications for completed operations has been added, displayed under the address bar as a small stripe overlaying the content. For instance, such a dialog can inform the user of a successful item addition to the reading list and show a button to open the reading list in the sidebar. The rollout of this new notification format will occur gradually, with a setting proposed to manage its display: chrome:\/\/flags\/#top-chrome-toasts.
<\/center>\n
With the energy saver mode enabled, experimental support for automatically freezing CPU-intensive tabs that are not producing sound and have been hidden for more than 5 minutes has been implemented. Exceptions are made only for tabs related to managing external devices or conducting video and audio conferences (such tabs are identified based on access to the API for working with USB, Bluetooth, cameras, input devices, and microphones, as well as establishing a communication channel using RTCDataChannel or MediaStreamTrack). To enable auto-freezing, settings chrome:\/\/flags\/#freezing-on-energy-saver and chrome:\/\/flags\/#freezing-on-energy-saver-testing have been added. In Chrome 131, auto-freezing is planned to be gradually enabled by default, starting with 1% of users.\n
The Android version features a built-in PDF document viewer that does not require calling external applications (there are options for downloading the PDF and opening it in a third-party application).\n
The ability to open not only videos but also any elements in picture-in-picture mode has been provided to display arbitrary content over other content. For example, in picture-in-picture mode, it is now possible to show interfaces for video conferences, custom video players, note-taking systems, chats, developer tools, etc. Opening content in picture-in-picture mode is accomplished using the documentPictureInPicture.requestWindow() method, which returns an object through which content can be added using the .document.body.append() method.
<\/center>\n
The ability to access external dictionaries with compressed responses using Brotli and Zstandard algorithms has been added.\n
Support for activating scroll areas during navigation using the keyboard has been introduced, allowing users without a mouse to first switch to the desired area using the Tab key and then scroll through its content using the arrow keys.\n
Support for parsing non-standard URL schemes (not included in the list of typical schemes) with host-path separation has been added. For example, when parsing the URL git:\/\/example.com\/path, the value example.com will be identified as the host, and \/path as the path (previously, \/\/example.com\/path was processed as a single path).\n
The Android version now features integrated support for connecting third-party form autofill and password saving providers, independent of the Accessibility API.\n
The behavior of the element is now consistent with Safari and Firefox \u2014 in the 'none' visibility mode, the element does not get hidden but switches to a separate style.\n
New recommendations from the CSS Working Group for handling nested rules in CSS blocks have been implemented, which now take into account the order of CSS property and rule definitions in the block (previously, all CSS rules were processed first, which led to illogical results from the developer's perspective). For example, the CSS block shown below used to set a red background color, but now it will set a green one: .foo { width: fit-content; @media screen { background-color: red; } background-color: green; }\n
The CSS property box-decoration-break has been implemented, indicating how to render an element when its parts are split across different lines, columns, or pages. There are two rendering modes available: slice \u2014 the element is first rendered fully and then cut into parts; clone \u2014 each fragment is rendered separately with its own borders and margins. In Firefox, this property has been supported since 2014.
<\/center>\n
The WebGPU API has introduced the 'dual-source-blending' mode for blending output from two fragment shaders with the result recorded in a single framebuffer.\n
In 'Origin trials' mode, the Language Detector API has been implemented, allowing language detection based on a text fragment.\n
The capabilities of web development tools have been expanded. A dropdown menu with additional filters has been added to the network activity analysis panel. An option has been added to clean sensitive data before saving the HTTP session in HAR (HTTP Archive) format. <\/ul>\n
<\/center>
\r\n \r\n
<\/div>\r\n <\/div> <\/center> <\/p>\n
In addition to new features and bug fixes, the latest version addresses 17 vulnerabilities. Many vulnerabilities were discovered as a result of automated testing using AddressSanitizer, MemorySanitizer, Control Flow Integrity, LibFuzzer, and AFL tools. One issue has been assigned a high severity level (accessing already freed memory in AI-related code). No critical issues that would allow bypassing all levels of browser protection and executing code outside of the sandbox environment have been found. As part of the bounty program for vulnerability discovery for this release, Google has paid out 13 rewards totaling $72,000 (one reward of $36,000, one of $4,000, and one of $3,000, two rewards of $6,000, $5,000, and $2,000, and three rewards of $1,000). The amount of one reward has yet to be determined. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Release](\"\/wp-content\/uploads\/2024\/10\/6733ffa254857870de9a80ea21de29ba.png\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2024\/10\/446c33ec9dde1747945b8b1fb7d17147.png\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2024\/10\/e221744236dc9dbc51114761ef4d7c4f.png\")
![\"Release](\"\/wp-content\/uploads\/2024\/10\/b9212f4da10f5a478ea67aa19f35d36a.png\")
<\/center>\n![\"Release](\"\/wp-content\/uploads\/2024\/10\/0b87bbdec3ea5674f507e55925c72b21.png\")
<\/center> ![\"Play](\"https:\/\/img.youtube.com\/vi\/_AERyyyBxWM\/hqdefault.jpg\")
\r\n