Chrome version: 125, 124, 123, 122, 121, 120, 119, 118, 117, 116, 115, 114, 113, 112, 111, 110, 109, 108, 107, 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0
This release of Chrome had 14 new features.
Render-initiated navigations to filesystem:// URLs are blocked in top-level frames, but for some reason allowed in iframes. As part of the storage partitioning efforts, we propose to remove support for third party contexts, and consistently block navigation to filesystem:// URLs everywhere. See https://chromestatus.com/metrics/feature/timeline/popularity/4077 for usage details (currently extremely low). #
This feature was specified in this Spec.
object-view-box allows the author to specify a subset within an image that should draw within the content box of the target replaced element. This enables an author to create an image with a custom glow or shadow applied, with proper ink-overflow behavior like a CSS shadow would have. #
This feature was specified in this Spec.
When cookies are set with an explicit Expires/Max-Age attribute the value will now be capped to no more than 400 days in the future. Previously, there was no limit and cookies could expire as much as multiple millennia in the future. #
This feature was specified in this Spec.
This adds three new CSS properties: translate, rotate, and scale. These properties are known as the individual transform properties (and were previously known as the independent transform properties). This exposes a simple way for web developers to access transforms in an intuitive way, without having to think about how functions in the transform property interact with each other. The properties are individually animatable. #
This feature was specified in this Spec.
Allows writing media queries using ordinary mathematical comparison operators, and adds support for 'or', 'not', nesting, and evaluation of "unknown" features. #
This feature was specified in this Spec.
Integrates the Web Bluetooth API with Permissions Policy, which should be identified by the "bluetooth" token. The Web Bluetooth API allows webpages to communicate with devices over Bluetooth. However, this API is not allowed to be used from cross-origin iframes. This integration enables this scenario while providing protection against unwanted access to Bluetooth capabilities, which requires the top-level document to explicitly allow a cross-origin iframe to use the API's methods. #
This feature was specified in this Spec.
Sends a warning-only CORS preflight request ahead of any private network requests for subresources, asking for explicit permission from the target server. If the preflight request fails due to Private Network Access checks, a warning is displayed in the DevTools issues panel, but the error is otherwise ignored. The subsequent request is sent as if the preflight had succeeded. A private network request is any request from a public website to a private IP address or localhost, or from a private website (e.g. intranet) to localhost. Sending a preflight request mitigates the risk of cross-site request forgery attacks against private network devices such as routers, which are often not prepared to defend against this threat. #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1FYPIeP90MQ_pQ6UAo0mCB3g2Z_AynfPWHbDnHIST6VI/edit
No linked samplesA set of 4 hints (`dpr`, `width`, `viewport-width`, and `device-memory`) have a default allowlist of `self` but behave as though they have a default allowlist of `*` on Android. The default allowlist of `*` goes against the Client Hints Infrastructure standard; fixing this will increase privacy on Android by requiring explicit delegation of these hints. #
This feature was specified in this Spec.
Provides a new approach to load a large number of resources efficiently using a format that allows multiple resources to be bundled, e.g. Web Bundles. #
This feature was specified in this Spec.
overflow-clip-margin specifies how far an element's content is allowed to paint before being clipped. This feature allows using visual-box values to configure the reference box that defines the overflow clip edge the content is clipped to. #
This feature was specified in this Spec.
The Cryptotoken component extension offers a chrome.runtime.sendMessage() API that allows any web site to make requests to a user's FIDO U2F security key. Cryptotoken and its API have been subsumed by the W3C Web Authentication API. #
This feature was specified in this Spec.
Web Custom formats let websites read and write arbitrary unsanitized payloads using a standardized web custom format, as well as read and write a limited subset of OS-specific formats (for supporting legacy apps). The name of the clipboard format is mangled by the browser in a standardized way to indicate that the content is from the web, which allows native applications to opt-in to accepting the unsanitized content. #
This feature was specified in this Spec.
Docs: https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#web-custom-formats-for-async-clipboard-apihttps://docs.google.com/document/d/1afc45MQuwxEWgoUeJCO-sOWRSzs31V4JS-kKXJNMTXw/edit
Samples: https://sequoia-innovative-date.glitch.me
Implementation of WebGL color management API WebGL allows specification of - the color space that its drawing buffer is - the color space that content should be converted to when importing as a texture This feature is to update our implementation to include this functionality. Prior to this feature, both of these defaulted to sRGB. Now they can also use "display-p3". #
This feature was specified in this Spec.
Samples: https://ccameron-chromium.github.io/webgl-examples/p3.html
Fullscreen Companion Window allows sites to place fullscreen content and a popup window on separate screens from a single user activation. This is a small requested enhancement of the Window Management feature: https://chromestatus.com/feature/5252960583942144 #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1RRlGQharWVnmxKTomfKhNiaeE31L7iXHeXVfifOvwJA
Samples: https://michaelwasserman.github.io/window-placement-demo
This release of Chrome had 1 new origin trials.
We introduce a performant and robust API for cropping a self-capture video track. (Recall that applications may *already* video-capture the tab in which the application is run using getDisplayMedia(). Using our new Region Capture, such an application may now *crop* that track and remove some content from it; typically before sharing it remotely.) #
This feature was specified in this Spec.
Samples: https://region-capture-demo.glitch.mehttps://w3c.github.io/mediacapture-region/demo
This release of Chrome had 0 are available behind a flag.
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:
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:
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.
This release of Chrome had 0 features deprecated.
This release of Chrome had 0 features removed.