Google company web browser release ... Simultaneously stable release of a free project , which is the basis of Chrome. Chrome browser the use of Google logos, the presence of a system for sending notifications in case of a crash, the ability to download a Flash module on demand, modules for playing protected video content (DRM), an automatic update system, and transmission on search . Chrome 81 was originally scheduled to be published on March 17th, but due to the SARS-CoV-2 coronavirus pandemic and developers moving to work from home, the release was . The next release of Chrome 82 will be , Chrome 83 is scheduled to release on May 19th.
:
- Implementation continued from loading mixed media content (when resources are loaded on an HTTPS page using the http:// protocol). Pages opened via HTTPS will now automatically replace "http://" links with "https://" when loading images, scripts, iframes, sound and video files was implemented in the last release. If the image is not available via https, then its loading is blocked (manually you can mark the blocking through the menu, accessible through the padlock symbol in the address bar).
- FTP protocol support. In the next release, all FTP related code from the codebase. It is recommended to use external FTP clients for FTP access. Temporarily, FTP support can be reverted using the "--enable-ftp" or "--enable-features=FtpProtocol" flag.
- For all users, the tab grouping feature is enabled, which allows you to combine several tabs that are similar in purpose into visually separated groups. Each group can have its own color and name. Previously, tab grouping was offered for testing only to a small percentage of users.
- In the API added device support . The WebXR API allows you to unify work with various classes of devices, from stationary virtual reality helmets to solutions based on mobile devices. A new API has been proposed for creating augmented reality applications , which allows you to place virtual objects in the field of view of the camera, which reflects reality. For example, you can a virtual flower on a window sill captured by the camera, display information labels on top of objects, or arrange virtual furniture, filming an empty room.
- When saving a password in the built-in password manager, a warning is displayed if the password is entered on an insecure site.
- Contributed to Google's terms of use (), in which appeared for Google Chrome and Chrome OS.
- Authentication using NTLM/Kerberos is disabled by default in incognito mode and guest session.
- The TLS 1.3 implementation includes extended mechanisms to resist rollback to earlier versions of the TLS protocol. Previously, protocol rollback protection was only partially enabled due to incompatibility with some misbehaving proxy servers (Palo Alto Networks PAN-OS, Cisco Firepower Threat Defense, ASA with FirePOWER). Compatibility issues are now a thing of the past, as most vendors of these proxies have released updates to bring their TLS implementations up to specification.
- Added the option "chrome://flags/#treat-unsafe-downloads-as-active-content" to the settings, which allows you to enable warnings when you try executable files from links from HTTPS pages (in Chrome 83, such warnings will be displayed by default, and in Chrome 84, downloads will be blocked).
- Added API support for mobile devices , which allows web applications to read and write NFC tags. Examples of using the new API in web applications include providing information about museum exhibits, conducting an inventory, obtaining information from the badges of conference participants, etc. Tags are sent and scanned using the NDEFWriter and NDEFReader objects. The new API is currently only available in the Origin Trials mode (experimental features that require a separate ). Origin Trial implies the ability to work with the specified API from applications downloaded from localhost or 127.0.0.1, or after registering and receiving a special token that is valid for a limited time for a specific site.
- In Origin Trial mode, a flag is proposed in the PointerLock API , when set, data on mouse movement events are transmitted in pure form, without corrections and acceleration.
- Stabilized and now distributed outside the Origin Trials API , which allows web applications to create indicators that are displayed on the panel or home screen. When the page is closed, the indicator is automatically removed. For example, in a similar way, you can display the number of unread messages or information about some events;
- Added to Media Session API tracking position when playing a song. You can get data about the playback speed, duration and current playback time, which allows you to create your own interfaces for estimating the position and moving around the track.
- The INTL API implements the method , through which you can get localized names of languages, countries, currencies, date elements, etc.
- In the API , designed to collect data on the state of resources while the user is working with the web application, the ability to use the "buffered" flag with long-running tasks.
- By default, when displaying images, Chrome will respect the orientation information from the EXIF ββmetadata. To explicitly override this behavior, the "image-orientation" CSS property is proposed.
- Added meta tag and CSS property "β, allowing you to select a color scheme for rendering interface elements such as form buttons and scrollbars.
- Attribute added to HTMLAnchorElement , through which you can send information about the need to translate the page into another language after clicking on the link.
- Added a new event type , which includes new properties that let you know the element whose call resulted in the form being submitted. For example, SubmitEvent makes it possible to use a single handler that is common to various buttons and links that result in a form submission.
- in web developer tools:
- Added "Copy > Copy as Node.js fetch" to the context menu shown for network requests for copying in the form of a fetch statement including Cookie data.
- Provided a tooltip with an unescaped data option when hovering the mouse over the "content" CSS property.
- In the web console, the detail of error messages when parsing fields in the source map has been increased.
- Added setting "Preferences > Sources > Allow scrolling past end of file" to disable scrolling past the end of the file when viewing the source text of the page.
- Moto G4 smartphone screen simulation has been added to the Device panel.
- In the Cookies panel, blocked Cookies are highlighted with a yellow background.
- Cookies tables displayed in the Network and Application panels now have a column with data on the priority of Cookie selection.
- All fields (except for the size field) in tables with Cookies are now editable.
- support for TLS 1.0 and TLS 1.1 protocols before the release of Chrome 84. Until the release of Chrome 83, the inclusion of clearance web forms that have been optimized for use on touch screens.
In addition to innovations and bug fixes, the new version eliminates . Many of the vulnerabilities were identified as a result of automated testing tools , , , ΠΈ . 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 Vulnerability Bounty program for the current release, Google has paid out 23 awards worth $26 (one $7500 award, one $5000 award, one 3000 award, two $2000 awards, three $1000 awards, and eight $500 awards). The amount of 7 rewards has not yet been determined.
Source: opennet.ru