Unless otherwise noted, changes described below apply to the newest Chrome Beta channel release for Android, Chrome OS, Linux, Mac, and Windows.
Native support means the browser can fetch granular dependencies in parallel, taking advantage of caching, avoiding duplications across the page, and ensuring the script executes in the correct order, all without a build step.
The PaymentRequest process throughout a transaction.
Web Share API
To allow users to easily share content on social networks, developers have had to manually integrate sharing buttons into their site for each social service. This often leads to users not being able to share with the services they actually use, in addition to bloated page sizes and security risks from including third-party code.
Sites can now use the new navigator.share API on Chrome for Android to trigger the native Android share dialog, allowing the user to easily share text or links with any of their installed native apps. In a future release, this API will also be able to share to installed web apps.
The navigator.share API allows the user to share content with a variety of native apps via the native Android share dialog.
Most hardware peripherals such as keyboards, mice, printers, and gamepads are supported by high-level web platform APIs. To use specialized educational, scientific, or industrial USB peripherals, users must find and install potentially unsafe drivers and software with system-level privileges.
Chrome now supports the WebUSB API, allowing web apps to communicate with peripherals given a user’s consent. This enables all the functionality provided by these devices, while still preserving the security guarantees of the web.
Developers can now specify scrolling smoothness via a new optional parameter in existing Scroll APIs or with the scroll-behaviorCSS property.
To prevent the use of mis-issued certificates from going unnoticed, sites can use the new Expect-CTHTTP header which will enable automated reporting and/or enforcement of Certificate Transparency requirements.
Chrome will no longer decode frames for videos using Media Source in background tabs.
To increase security, resources with URLs containing both n and < characters will now be blocked.
To increase security, support for the Presentation API’sstart function has been deprecated and removed for insecure contexts.
To increase consistency across on<event> attributes, onwheel attributes have been moved from Element to Window, Document, HTMLElement, and SVGElement.
To better follow spec and provide more granular control over the flow of referred content, Chrome now supports three new Referrer Policy values, same-origin, strict-origin, and strict-origin-when-cross-origin.
Following the change in spec, the maximum value for colSpan has been decreased from 8190 to 1000.