Chrome Release Summary
+151
Chrome 86
Enabled (22) | Origin Trial (8) | Behind a flag (3) | Deprecated (0) | Removed (1)Enabled by default in 86
This release of Chrome had 22 new features.
A well-known URL for changing passwords
Websites can set a well-known URL for changing password `/.well-known/change-password` to be redirected to its change password page to help users change their password quickly. Chrome leverages this URL to help users change their passwords when it detects a weak password in the user's password storage. #
This feature was specified in this Spec.
Altitude/Azimuth for PointerEvents v3
Adds Altitude/Azimuth angles to PointerEvents. Adds TiltX/TiltY to Altitude/Azimuth transformation and Altitude/Azimuth to TiltX/TiltY transformation depending which pair is available from the device. #
Resources
Docs: https://docs.google.com/document/d/1BkJDlHJvR6jndtJys7IYuqwITgVi6P9iOnfA0z5Cu04/edit?usp=sharing
No linked samplesAutoupgrade Image Mixed Content
This feature will autoupgrade optionally-blockable mixed content (HTTP content in HTTPS sites) by rewriting the URL to HTTPS, without a fallback to HTTP if the content is not available over HTTPS. Image mixed content autoupgrades by default are targeted for M86. Audio/Video mixed content autoupgrades are separately tracked in https://www.chromestatus.com/feature/5557268741357568 #
Resources
Docs: https://docs.google.com/document/d/1dp-kuN25wnEbMPNWBxM8LvOjyeydWpXPklNnGcsWK1o/edit
No linked samplesBack-forward cache on Android
Creates a cache for pages which allows for instant navigations to previously-visited pages after cross-site navigations. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1mrgp7XzR16rd1xqFYOJgC1IP0NPLZFaRU5Ukj3-TlLwhttps://web.dev/bfcache/https://github.com/rakina/bfcache-explainer#what-is-bfcache
No linked samplesCSS ::marker pseudo-element
The ::marker pseudo-element represents the automatically generated marker box of a list item. Like ::before and ::after, ::marker is a tree-abiding pseudo-element, so it always fit within the box tree. But unlike ::before and ::after, currently it only accepts a small subset of safe properties, because the marker box layout is mostly undefined. Note this intent only covers ::marker, not ::before::marker nor ::after::marker (see crbug.com/1097992). #
This feature was specified in this Spec.
Resources
Docs: https://drafts.csswg.org/css-pseudo-4/#marker-pseudohttps://drafts.csswg.org/css-lists-3/#marker-pseudo
No linked samplesCSS Selectors 4 Pseudo-Class :focus-visible
The :focus-visible pseudo-class makes it easier for developers to create focus styles that appropriately match the user's input modality. It is designed to help prevent a common anti-pattern where developers remove focus outlines for mouse users, and inadvertently make their sites inaccessible to keyboard users. #
This feature was specified in this Spec.
Change MediaSettingsRange & PhotoCapabilities interfaces to dictionaries
Aggregates and logs media settings ranges and photo capabilities in JSON. Changing MediaSettingsRange and PhotoCapabilities interfaces to dictionaries will improve developer ergonomics by allowing web developers to easily log and aggregate exposureCompensation, exposureTime, colorTemperature, iso, brightness, contrast, saturation, sharpness, focusDistance, pan, tilt, zoom, and photo capabilities (redEyeReduction, imageHeight, imageWidth, fillLightMode). #
This feature was specified in this Spec.
Document-Policy header
Document Policy restricts the surface area of the web platform on a per-document basis, similar to iframe sandboxing, but more flexibly. It can do things like: - Restrict the use of poorly-performing images - Disable slow synchronous JS APIs - Configure iframe, image, or script loading styles - Restrict overall document sizes or network usage - Restrict patterns which cause page re-layout This is just the HTTP header used to set a policy on a document, separate from any features. #
This feature was specified in this Spec.
Resources
Docs: https://w3c.github.io/webappsec-permissions-policy/document-policy.htmlhttps://github.com/w3c/webappsec-permissions-policy/blob/master/document-policy-explainer.md
No linked samplesDocument-Policy: force-load-at-top
ForceLoadAtTop provides an opt-out for Scroll To Text (and other load-on-scroll behaviors as they are also affected by the issues raised in https://github.com/WICG/scroll-to-text-fragment/issues/76) for privacy sensitive sites, as discussed in https://github.com/WICG/scroll-to-text-fragment/issues/80. The ForceLoadAtTop feature allows sites to indicate that they should always be loaded at the top of the page, blocking any scroll-on-load behaviors including text fragments, element fragments, and #
This feature was specified in this Spec.
Resources
Docs: https://github.com/WICG/scroll-to-text-fragment#opting-out
No linked samplesFetchEvent.handled
A FetchEvent dispatched to a service worker is in a loading pipeline, which is performance sensitive. The new FetchEvent.handled property returns a promise that resolves when a response is returned from a service worker to its client. This enables a service worker to delay tasks that can only run after responses are complete. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/w3c/ServiceWorker/issues/1397
Samples: https://github.com/w3c/ServiceWorker/issues/1397#issuecomment-479036562
File System Access
This API enables developers to build powerful apps that interact with other (non-Web) apps on the user’s device via the device’s file system. After a user grants a web app access, this API allows the app to read or save changes directly to files and folders selected by the user. Beyond reading and writing files, this API provides the ability to open a directory and enumerate its contents, as well as store file and directory handles in IndexedDB to later regain access to the same content. #
This feature was specified in this Spec.
Resources
Docs: https://web.dev/file-system-access/https://web.dev/browser-nativefs/
Samples: https://github.com/GoogleChromeLabs/text-editorhttps://googlechromelabs.github.io/text-editor/
HTMLMediaElement.preservesPitch
Adds a property to determine whether the pitch of an audio or video element should be preserved when adjusting the playback rate. #
This feature was specified in this Spec.
Imperative Shadow DOM Distribution API
Web developers can specify node-to-slot assignments imperatively in Shadow DOM slotting. Please see the spec discussion [1] and the explainer [2]. - [1] https://github.com/whatwg/html/issues/3534 - [2] https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Imperative-Shadow-DOM-Distribution-API.md #
This feature was specified in this Spec.
Resources
No linked samplesIntensive throttling of Javascript timer wake ups
In a Window whose top Window has been hidden for 5 minutes and which is not opted out from intensive wake up throttling, a timer task with non-zero timeout can run: - on a 1-second aligned wake up if: - the timer task's nesting level is < 5, or, -the Window is same-origin with the top Window and at least 1 minute has elapsed since the last timer task with nesting level >= 5 has run in any Window in the tree that is same-origin with the top Window - on a 1-minute aligned wake up, otherwise. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/11FhKHRcABGS4SWPFGwoL6g0ALMqrFKapCk5ZTKKupEk/edit?usp=sharing
No linked samplesParentNode.replaceChildren() Method
Replaces all children of the ParentNode with the passed-in nodes. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/whatwg/dom/issues/478
No linked samplesPercent-encode U+007F DELETE when parsing URLs
When parsing URLs, encode the character U+007F DELETE as "%7F". This improves readability, reduces spoofing risk, makes Chrome's behavior more consistent, interoperable with other browsers and compliant with the specification. #
This feature was specified in this Spec.
Safelist distributed web schemes for registerProtocolHandler()
Extend the list of URL schemes that can be overridden via registerProtocolHandler() to include "cabal", "dat", "did", "dweb", "ethereum", "hyper", "ipfs", "ipns", and "ssb". #
This feature was specified in this Spec.
Resources
Docs: https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers
No linked samplesThird-party origin trials
Origin trials can now be enabled by embedded scripts, based on tokens matching their third-party origin. Previously, it was possible for scripts to enable origin trials, but only when the token matches the origin of the containing document. #
Resources
Docs: https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/explainer.mdhttps://docs.google.com/document/d/1xALH9W7rWmX0FpjudhDeS2TNTEOXuPn4Tlc9VmuPdHA/edithttps://web.dev/third-party-origin-trials
No linked samplesWebRTC Insertable Streams
This API enables the insertion of user-defined processing steps in the encoding and decoding of a WebRTC MediaStreamTrack. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/w3c/webrtc-insertable-streams
No linked samplesdisplay:inline-grid/grid/inline-flex/flex for <fieldset>
The FIELDSET element will support 'inline-grid', 'grid', 'inline-flex' and 'flex' keywords for CSS 'display' property. #
This feature was specified in this Spec.
document.fragmentDirective
This change moves window.location.fragmentDirective to document.fragmentDirective which seems like a more appropriate and safer place. It is a small change to the text-fragments feature in https://chromestatus.com/feature/4733392803332096. Text-fragments introduced an empty object at window.location.fragmentDirective as a means to feature detect the newly added text-fragment capability. window.location turns out to be a bad place for this functionality, see https://crbug.com/1057795. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/WICG/scroll-to-text-fragment/
No linked samplestext/html support for async clipboard api
The async clipboard api currently does not support the text/html format. This feature adds support for copying and pasting html from the clipboard. The HTML is sanitized when it is read and written to the clipboard. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1tzjfckWUKAAxEbKcUjg21uz7LFDMQ7ZDzfTTj3Lp93Y/
Samples: https://hyper-silly-cross.glitch.me/
Origin Trials in-progress in 86
This release of Chrome had 8 new origin trials.
Back-forward cache for same-site navigations on Android
Creates a cache for pages which allows for instant navigations to previously-visited pages after all eligible navigations on Android, both cross-site and same-site. This enhances the original version of back-forward cache, which only caches pages on cross-site navigations: https://chromestatus.com/feature/5815270035685376. This enhancement shipped by default in M95. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1mrgp7XzR16rd1xqFYOJgC1IP0NPLZFaRU5Ukj3-TlLwhttps://web.dev/bfcache/https://github.com/rakina/bfcache-explainer#what-is-bfcache
No linked samplesBack-forward cache on Android
Creates a cache for pages which allows for instant navigations to previously-visited pages after cross-site navigations. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1mrgp7XzR16rd1xqFYOJgC1IP0NPLZFaRU5Ukj3-TlLwhttps://web.dev/bfcache/https://github.com/rakina/bfcache-explainer#what-is-bfcache
No linked samplesCross-origin opener policy reporting API
Adds a reporting API to help developers deploy cross-origin opener policy. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/camillelamy/explainers/blob/master/coop_reporting.md
No linked samplesHidden=until-found HTML attribute and beforematch event
This feature extends the existing hidden attribute with a new value, "until-found", which makes the element searchable by find-in-page, scroll to text fragment, and fragment navigation. When these search/navigation features want to scroll to something inside a hidden=until-found element, the browser removes the hidden attribute from the element and fires the "beforematch" event on it so that the newly revealed content can be scrolled into view. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/WICG/display-locking/blob/master/explainers/hidden-content-explainer.md
No linked samplesNotification Triggers
Adds the showTrigger property to the Notification interface to enable showing a notification at a specific time in the future, even if the device is offline. Websites can use this to schedule notifications without using push messages. #
Resources
Docs: https://web.dev/notification-triggers/
No linked samplesScheduling APIs: Prioritized scheduler.postTask
Userspace tasks often have varying degrees of importance (related to user experience), but the Platform lacks a unified API to schedule prioritized work. The postTask API allows developers to schedule tasks (javascript callbacks) with a native browser scheduler at 3 levels of priority: user-blocking, user-visible, and background. It also exposes a TaskController, which can be used to dynamically cancel tasks and change their priority. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1Apz-SD-pOagGeyWxIpgOi0ARNkrCrELhPdm18eeu9tw/edit?usp=sharing
Samples: https://github.com/WICG/scheduling-apis/blob/main/explainers/prioritized-post-task.mdhttps://github.com/WICG/main-thread-scheduling/tree/master/sample-code
Support for WebHID
The [WebHID API](https://developer.chrome.com/docs/extensions/how-to/web-platform/webhid) enables web applications to interact with Human Interface Devices (HIDs) over USB and Bluetooth beyond standard system input mappings (such as mice, keyboards, touchscreens, and standard gamepads). Web applications can request user permission to connect to HID devices, send and receive input, output, and feature reports, and inspect report descriptors. WebHID shipped on [desktop platforms](https://developer.chrome.com/docs/capabilities/web-apis/hid-examples) (Windows, macOS, Linux, and ChromeOS) in Chrome 89. Chrome 158 brings the existing WebHID API to Chrome on Android (relying on new OS support in Android 17 / API level 37 and later) with no changes to the web-exposed API surface. Popular uses today include customizing mechanical keyboards, keypads, and gaming mice, calibrating gamepads, and integrating hardware headset call controls in call centers. WebView is not supported, as it does not have a device chooser UI or permissions UX controls. This feature can be controlled using the following enterprise policies: * [DefaultWebHidGuardSetting](https://chromeenterprise.google/policies/#DefaultWebHidGuardSetting) * [WebHidAllowAllDevicesForUrls](https://chromeenterprise.google/policies/#WebHidAllowAllDevicesForUrls) * [WebHidAllowDevicesForUrls](https://chromeenterprise.google/policies/#WebHidAllowDevicesForUrls) * [WebHidAllowDevicesWithHidUsagesForUrls](https://chromeenterprise.google/policies/#WebHidAllowDevicesWithHidUsagesForUrls) * [WebHidAskForUrls](https://chromeenterprise.google/policies/#WebHidAskForUrls) * [WebHidBlockedForUrls](https://chromeenterprise.google/policies/#WebHidBlockedForUrls) For more details, see [Set ChromeOS devices policies](https://support.google.com/chrome/a/answer/1375678) in the Chrome Enterprise and Education Help Center. #
This feature was specified in this Spec.
Resources
Docs: https://web.dev/hid/https://web.dev/hid-examples/
No linked samplesWebCodecs
Provides efficient, low-level access to built-in (software and hardware) media encoders and decoders. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/WICG/web-codecs/blob/master/explainer.md
No linked samplesFlagged features in 86
This release of Chrome had 3 are available behind a flag.
Restrict "private network requests" for subresources from public websites to secure contexts.
Requires that private network requests for subresources from public websites may only be initiated from a secure context. Examples include internet to intranet requests and internet to loopback requests. This is a first step towards fully implementing Private Network Access: https://wicg.github.io/private-network-access/ #
This feature was specified in this Spec.
Resources
No linked samplesRestrict Gamepad usage
Requires a secure context for the Gamepad API and adds a feature policy to allow restricting gamepad use. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1Dj_7EpT9ttnI96BuNXtLEJkHEq0orHgoLeYaOBz9xsU/edit?usp=sharing
No linked samplesWebXR Raw Camera Access
Allows applications authored against the WebXR Device API to access pose-synchronized camera image textures from within WebXR sessions. #
This feature was specified in this Spec.
Resources
Docs: https://github.com/immersive-web/raw-camera-access/blob/main/explainer.mdhttps://immersive-web.github.io/raw-camera-access
Deprecations and Removals
Deprecation policy
To keep the platform healthy, we sometimes remove APIs from the Web Platform which have run their course. There can be many reasons why we would remove an API, such as:
- They are superseded by newer APIs.
- They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
- They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.
Some of these changes will have an effect on a very small number of sites. To mitigate issues ahead of time, we try to give developers advanced notice so they can make the required changes to keep their sites running.
Chrome currently has a process for deprecations and removals of API's, essentially:
- Announce on the blink-dev mailing list.
- Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
- Wait, monitor, and then remove the feature as usage drops.
You can find a list of all deprecated features on chromestatus.com using the deprecated filter and removed features by applying the removed filter. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.
Deprecated features in 86
This release of Chrome had 0 features deprecated.
Removed features in 86
This release of Chrome had 1 features removed.
EME persistent-usage-record session
Support a new MediaKeySessionType “persistent-usage-record session”, for which the license and key(s) are not persisted and for which a record of key usage is persisted when the keys available within the session are destroyed. #
This feature was specified in this Spec.