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 10 new features.
Changes the default style for ::placeholder from #757575 to rgba(0, 0, 0, 0.54). #
This feature was specified in this Spec.
The CSS Properties and Values API spec defines a registerProperty() function which can be called from JavaScript to register typed and animatable custom CSS properties. This API expands the existing CSS custom properties to improve usability of other Houdini APIs. Being able to animate these and customize inheritance and initial values makes it more useful for custom layout/paint, and having types associated with these allows the typed object mode to work more effectively with custom properties. #
This feature was specified in this Spec.
Chrome now disallows synchronous XHR during page dismissal when the page is being navigated away from or closed by the user. This involves the following events (when fired on the path of page dismissal): beforeunload, unload, pagehide, and visibilitychange. A temporary opt-out is available via Origin Trial "Allow Sync XHR In Page Dismissal": https://developers.chrome.com/origintrials/#/trials/active #
This feature was specified in this Spec.
This implements byte-for-byte update check for service worker scripts imported by importScripts(). #
This feature was specified in this Spec.
In cases where there is something wrong with the payment response's data (e.g., you find out that the shipping address is a PO box), the retry() method of a PaymentResponse instance allows you to ask a user to retry a payment. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponse/retry
Samples: https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponse/retry
Adds support for percentage values to the opacity properties, specifically, opacity, stop-opacity, fill-opacity, stroke-opacity, and shape-image-threshold. For example, opacity: 50%; is equivalent to opacity: 0.5; https://drafts.csswg.org/css-color/#transparency #
This feature was specified in this Spec.
Docs: https://www.w3.org/TR/css-color-4/#transparencyhttps://www.w3.org/TR/css-color-4/#typedef-alpha-value
No linked samplesRemoves fine-grained information from the shipping address before exposing it to the merchant website in ShippingAddressChange event. #
This feature was specified in this Spec.
Docs: N/A
No linked samplesAdds a media session action handler for "seekto". An action handler is an event tied specifically to a common media function such as pause or play. The "seekto" action handler will be called when the site should move the playback time to a specific time. This also adds a MediaSessionActionDetails dictionary that will be passed when an action handler is called. Use this as a basis for passing additional data for "seekbackward", "seekforward" and "seekto". #
This feature was specified in this Spec.
Docs: N/A
Samples: https://beccahughes.github.io/media/media-session-seeking/index.html
User Timing Level 3 extends the existing User Timing API to enable two new use cases: 1. Developers can pass custom timestamps to performance.measure() and performance.mark(), so as to conduct measurement across arbitrary timestamps. 2. Developers can report arbitrary metadata with performance.mark() and performance.measure(), which provides rich data to analytics via a standardized API. #
This feature was specified in this Spec.
getAvailability() returns a promise that resolves with true if the user agent is running on a system that has a Bluetooth radio and false otherwise. The powered state of the Bluetooth radio does not influence the availability because applications can prompt users to turn on the radio using requestDevice(). The availabilitychanged event can be used to detect changes in the availability of the Bluetooth radio. #
This feature was specified in this Spec.
Docs: https://chromium-review.googlesource.com/c/chromium/src/+/1651516
Samples: https://googlechrome.github.io/samples/web-bluetooth/availability.htmlhttps://googlechrome.github.io/samples/web-bluetooth/availability-async-await.html
This release of Chrome had 0 new origin trials.
This release of Chrome had 2 are available behind a flag.
Stops certain methods from snapping values to physical pixels, specifically scrollTop(), scrollLeft(), scrollX(), scrollY(), scrollTo(), and so on. Currently, calling window.scrollTo(0, 123.678) will snap the scroll offset to the nearest physical pixel. On a device with devicePixelRatio equal to 2 this would be 123.5, which is what is returned after this change. #
This feature was specified in this Spec.
Docs: https://github.com/bokand/RenderingIndependentScrollOffsets/blob/master/README.md
No linked samplesExpands the JavaScript API surface of WebAssembly to allow reflection on the data types of functions imported and exported from a WebAssembly module. #
This feature was specified in this Spec.
Docs: https://github.com/WebAssembly/js-types/blob/master/proposals/js-types/Overview.md
No linked samplesTo 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.
Remove the XSS Auditor from Chrome. #
This feature was specified in this Spec.
Docs: https://www.chromium.org/developers/design-documents/xss-auditorhttps://groups.google.com/a/chromium.org/g/blink-dev/c/TuYw-EZhO9g/m/blGViehIAwAJ
No linked samples