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 18 new features.
'-webkit-appearance' CSS property will have new 'auto' keyword, which indicates the default appearance of the target element. #
This feature was specified in this Spec.
Docs: N/A
No linked samplesTweak web font loading, so that: - Web fonts with 'font-display: optional' never cause relayout - Web font preloading is allowed to slightly block rendering (for all font-display values), so that if the font loads fast enough, we don't need to render with fallback. Therefore, when 'font-display: optional' and preloading are used together, we'll never see layout shifting from font swapping, and still have a good chance to use the font if it loads fast enough (e.g., from disk cache). #
This feature was specified in this Spec.
Docs: https://bit.ly/36E8UKB
No linked samplesAdds a function that queries whether a user agent supports a selector. #
This feature was specified in this Spec.
Docs: None.
Samples: The 3 tests below is for testing feature query function of css selector.https://github.com/web-platform-tests/wpt/blob/master/css/css-conditional/at-supports-040.htmlhttps://github.com/web-platform-tests/wpt/blob/master/css/css-conditional/at-supports-041.htmlhttps://github.com/web-platform-tests/wpt/blob/master/css/css-conditional/at-supports-042.html
Support the new markup in the ARIA annotations editor’s draft (3 new roles, 1 new property): suggestion, mark, comment, aria-description This feature enables new semantics: - Comments - Text highlights with semantic meaning, just like <mark> - Suggestions for changes, e.g. by another author in a Google Doc - Additional related information to be semantically tied to an element, allowing descriptions, definitions, footnotes and comments to be tied to another element. #
This feature was specified in this Spec.
Docs: -
Samples: https://codepen.io/aleventhal/full/VxByVK/
The Barcode Detection API is a subset of the Shape Detection API which provides the ability to detect and decode barcodes in an image provided by script. The image may come from any type of image buffer source such as an <image>, <video> or <canvas> tag. Some native platforms include built-in libraries for performing text detection and optical character recognition (OCR) in images. The availability of these libraries means that developers do not need to include a large third party library. #
This feature was specified in this Spec.
Docs: https://web.dev/shape-detection/https://docs.google.com/document/d/1QeCDBOoxkElAB0x7ZpM3VN3TQjS1ub1mejevd2Ik1gQ/edit
Samples: https://paul.kinlan.me/barcode-detection/https://web.dev/shape-detection/#barcodedetector
The contain-intrinsic-size property allows developers to specify a placeholder size which would be used while contain: size is applied. With contain-intrinsic-size specified, elements lay out as if they had a single child with fixed size (specified by contain-intrinsic-size) unless they have an explicit width/height. This is helpful when size containment may be dynamically added/removed so that there is a fallback size during size containment but a content-based size during regular sizing. #
This feature was specified in this Spec.
Docs: https://github.com/w3c/csswg-drafts/issues/4229
No linked samplesAdd a new HTTP header that prevents documents and workers from loading non-same-origin requests unless explicitly allowed via CORS or CORP. Combined with Cross-Origin-Opener-Policy (COOP), this feature allows documents (and workers) to use powerful APIs such as SharedArrayBuffer. #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1zDlfvfTJ_9e8Jdc8ehuV4zMEu9ySMCiTGMS9y0GU92k/edit
No linked samplesThe Cross-Origin-Opener-Policy response header provides a way for a document to request a new browsing context group to better isolate itself from other untrustworthy origins. Optionally, browsers can also choose to place top-level documents in a different process from documents without a matching Cross-Origin-Opener-Policy. #
This feature was specified in this Spec.
Docs: https://github.com/whatwg/html/issues/3740
No linked samplesJavaScript will support modules in shared workers. Setting 'module' type by the constructor's type attribute, worker scripts are loaded as ES modules and the import statement is available on worker contexts. #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1sSdYdSOLd5zvnNGeVNlBqfTZs_VRPIrrigV3SlMnWjg/edit?usp=sharing
No linked samplesHTMLVideoElement.requestVideoFrameCallback() registers a one-shot callback, called when a video frame has been presented for composition. It also provides useful metadata about that frame. #
This feature was specified in this Spec.
Docs: https://web.dev/requestvideoframecallback-rvfc/
No linked samplesExposes an optional relaxedDurability parameter on IDBDatabase.transaction to control flushing to disk. #
This feature was specified in this Spec.
This encoding parameter allows developers to limit the framerate on a video layer before sending. #
This feature was specified in this Spec.
Docs: n/a
No linked samplesWhen encoding video, and some constraint (bandwidth, CPU) prevents encoding at the configured framerate and resolution, the encoder must make a choice on how to modify the encoding parameters. An attribute is defined for RTCRtpSendParameters that allows this to be explicitly indicated for an RTCRtpSender. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpSendParameters
No linked samplesAccording to the HTML spec, <input type=time>, which allows users to input time in hours, minutes, and seconds, should support reversed ranges because it has a defined maximum of "23:59:59". A reversed range is when the input has a min and max attribute where the max is less than the min, and in this state, the input should allow values which are less than the min or greater than the max, but not in between them. This has been in the spec for many years but has not been implemented until now. #
This feature was specified in this Spec.
Docs: See summary above
Samples: https://input-reversed-range.glitch.me/
The CSS Paged Media Module Level 3 spec includes a list of page size names that may be used in the "size" property of the @page rule. Among these are two names for Japanese Industrial Standard page sizes which are currently not being recognized by Chrome: “JIS-B5” refers to JIS B5 size (182mm wide by 257mm high) “JIS-B4” refers to JIS B4 size (257mm wide by 364mm high) This feature completes the implementation of this section of the standard by adding support for these two page size. #
This feature was specified in this Spec.
Docs: N/A
No linked samples'Trusted Types' offers an (optional) mechanism for web sites to protect themselves against XSS (cross-site scripting) attacks.It limits the attack surface from potentially the entire code base to a handful of "policies" that a developer can implement and install, and whose usage the browser will then enforce. "Trusted types" then ensure that all risk-ful parts of the DOM can only be used by data that has gone through such a developer-supplied policy. Release is expected in Chrome 83. #
This feature was specified in this Spec.
Docs: https://w3c.github.io/webappsec-trusted-types/dist/spec/
Samples: https://web.dev/trusted-types/
Allows WebXR applications using immersive-ar on handheld devices to optionally activate a DOM overlay mode where the 2D page content is shown as an interactive transparent layer on top of the application-drawn WebGL content and camera image. While the current implementation is limited to ARCore-based handheld devices, the specification is intended to also support implementation on AR headsets. #
This feature was specified in this Spec.
Samples: https://klausw.github.io/three.js/examples/webvr_lorenzattractor.htmlhttps://klausw.github.io/a-frame-car-sample/index.htmlhttps://storage.googleapis.com/chromium-webxr-test/latest.html?target=proposals/index.html
The 'display' keywords 'inline-grid', 'grid', 'inline-flex', and 'flex' property will now function with <button> when align item is applied. #
This feature was specified in this Spec.
Samples: https://codepen.io/jpmedley/pen/MWwmoQE
This release of Chrome had 0 new origin trials.
This release of Chrome had 1 are available behind a flag.
When a fill forward animation finishes, it remains in effect. If enough of these animations build up, they can negatively impact performance and leak memory. There are 3 main parts to this feature: 1) Automatically remove animations that no longer contribute to the effect stack and fire remove events. 2) Animation.persist() to force an animation to remain that would otherwise be removed. 3) Animation.commitStyle() to inject an inline style based on the current property values. #
This feature was specified in this Spec.
Docs: https://drafts.csswg.org/web-animations/#replacing-animations
Samples: wpt/web-animations/interfaces/Animation/commitStyles.htmlwpt/web-animations/interfaces/Animation/style-change-events.htmlwpt/web-animations/interfaces/Animation/persist.html
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 1 features removed.
Sandboxed iframe can initiate or instantiate downloads. Chrome is planning on removing this capability - i.e. Chrome is going to block all downloads initiated from or instantiated in a sandboxed iframe by default. The embedder may add "allow-downloads" to the sandbox attributes list to opt in. This allows content providers to restrict malicious or abusive downloads. #
This feature was specified in this Spec.
Docs: Spec:https://github.com/whatwg/html/pull/4293Spec discussions:https://github.com/whatwg/html/issues/3236Design Doc:https://docs.google.com/document/d/1XfLQd9IbJBPAE4IAOvu4EubUaLuICJrDlrmz0Ya_mqQ
No linked samples