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 15 new features.
This is a new flag for `<iframe sandbox="...">` which will allow embedders to have control over whether an iframe can start a presentation session. #
This feature was specified in this Spec.
Apply the unicode flag to `pattern' attribute values. Syntax checking will be stricter, and '.' matches to a surrogate pair, and some other benefits. #
This feature was specified in this Spec.
Docs: https://mathiasbynens.be/notes/es6-unicode-regex
No linked samplesRelax autoplay restrictions to allow muted videos to autoplay. They will only be able to play while muted and unmuting will pause if not coming from a user gesture. #
This feature was specified in this Spec.
Docs: https://github.com/whatwg/html/issues/976
Samples: https://googlechrome.github.io/samples/muted-autoplay/index.html
The user-select property enables authors to specify which elements in the document can be selected by the user and how. Chrome has supported only prefixed version: -webkit-user-select. With -webkit-user-select:all value, the content of the element must be selected atomically: If a selection would contain part of the element, then the selection must contain the entire element including all its descendants. #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1158E0YvlUJ5Lwd-8XZBFqE2Ow_FWLrNVik1MFqk3WRU/edit?usp=sharing
No linked samplesAccording to the UI Events specification un-trusted events (i.e. those created by JavaScript) should not invoke the default action. 'click' is the only event that is a legacy permitted case. The isTrusted support was added in https://www.chromestatus.com/features/6461137440735232 which identifies trusted events from un-trusted events. We wish to prevent synthetic events from executing the default action, aligning with Firefox and IE. #
This feature was specified in this Spec.
3D-positioned descendants will be flattened by an ancestor that has opacity. Previously it did not, if that ancestor also specified transform-style: preserve-3d #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1xdOyUKXYCKKcMJd8fFyuG0JLTi72ajqQx8h1w1MXKWw/edit#
Samples: https://googlechrome.github.io/samples/css-opacity-force-flattening/index.html
The contentWindow property returns the Window object of an <Object> element. This attribute is read-only, but its properties can be manipulated like the global Window object. #
This feature was specified in this Spec.
Per recent MSE spec change [1], MSE objects should have EventHandler attributes for their various events. The logic for the events does not change; this feature just adds support for them via EventHandler attributes. [1] https://github.com/w3c/media-source/pull/75 #
This feature was specified in this Spec.
Docs: https://github.com/w3c/media-source/issues/66https://github.com/w3c/media-source/pull/75
No linked samplesSupport for the new format of MediaStreamTrack constraints. Support for the API calls for getting, setting and querying constraints on a MediaStreamTrack. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack
No linked samplesA badge image may be used to represent a notification when there is not enough space to display the notification itself. It may also be displayed inside the notification, but then it should have less visual priority than the notification icon. #
This feature was specified in this Spec.
Docs: https://github.com/whatwg/notifications/issues/65https://github.com/whatwg/notifications/pull/67
Samples: https://tests.peter.sh/notification-generator/
Adds the API navigator.mediaDevices.getUserMedia(), which returns a promise. As part of this feature, also release the unprefixed version of navigator.getUserMedia(), which uses callbacks. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/docs/Web/API/MediaDevices/getUserMediahttps://developers.google.com/web/updates/2015/10/media-devices
No linked samplesAll content will be re-rastered when its transform scale changes, iff it does not have the will-change: transform CSS property. In other words, `will-change: transform` means "please animate it fast". This only applies to transforms scales that happen via script manipulation, and does not apply to CSS animations. This means your site will likely get better-looking content, but it may also be slower without some simple changes outlined below. #
This feature was specified in this Spec.
Docs: https://docs.google.com/document/d/1f8WS99F9GORWP_m74l_JfsTHgCrHkbEorHYu72D4Xag/
Samples: https://googlechrome.github.io/samples/css-will-change-transform-rasterization/index.html
The new Shadow DOM APIs, called *v1*, including, but not limited to: - Element.attachShadow - New HTML Element: HTMLSlotElement - Slotable.assignedSlot - Event.composed, Event.composedPath() See http://hayato.io/2016/shadowdomv1/ for the difference between v0 and v1. Intent to Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zrZRD2ls5tw #
This feature was specified in this Spec.
Docs: https://developers.google.com/web/fundamentals/web-components/shadowdom
No linked samplesCSS Filters without the -webkit- prefix. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/filter
Samples: http://simpl.info/cssfilters/https://docs.webplatform.org/wiki/tutorials/css_filters
The existing lowpass and highpass BiquadFilter implementation has a defect where valid filters cannot be represented. To fix this, the filter formulas were updated. However, the new formulas will cause a change in the output of the filters. #
This feature was specified in this Spec.
Docs: http://webaudio.github.io/web-audio-api/#filters-characteristics
Samples: https://github.com/GoogleChrome/web-audio-samples/wiki/Detection-of-lowpass-BiquadFilter-implementationhttps://rtoy.github.io/webaudio-hacks/more/biquad/biquad-lowpass-q.html?usedB=true
This release of Chrome had 0 new origin trials.
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 1 features deprecated.
FileError was removed from File API (https://w3c.github.io/FileAPI/) after Chrome shipped the feature. This surfaces on: FileReader.error, FileWriter.error, and in the FileSystem API passed to the ErrorCallback (async) and thrown (sync) Other browsers do not use this, returning DOMError instead, which is itself being deprecated in favor of DOMException. The interface has been deprecated since 2013. In Chrome 53 we're adding a console warning. Removal is anticipated in Chrome 54. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/FileError
No linked samplesThis release of Chrome had 4 features removed.
The PaymentAddress interface has a careOf field which is non-standard (no well-known address standards support it, see below). The careOf field is unnecessary, the recipient and organization fields sufficiently support all necessary use cases. Adding careOf poses significant issues in terms of interoperability with existing postal address schemas and APIs. (From spec discussion: https://github.com/w3c/browser-payment-api/issues/244) #
This feature was specified in this Spec.
Docs: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/WhUAKyc0O80
No linked samplesThe HTML specification was changed so that LABEL element isn't a form-associated element. - Remove `form' content attribute support from LABEL element - Change the behavior of `form' IDL attribute of LABEL element so that it returns the form owner of the associated control. #
This feature was specified in this Spec.
Last year, we raised the minimum TLS Diffie-Hellman group size from 512-bit to 1024-bit. As mentioned then, 1024-bit is insufficient for the long-term. However, metrics report that around 95% of DHE connections seen by Chrome use 1024-bit DHE. This, compounded with how DHE is negotiated in TLS, makes it difficult to move past 1024-bit. Servers should upgrade to ECDHE if available. Otherwise, ensure a plain-RSA cipher suite is enabled. #
This feature was specified in this Spec.
Samples: https://dh1024.badssl.com/
The TextEncoder API never supported legacy encodings (such as 'shift_jis', 'windows-1252', etc) except for two UTF-16 variants ('utf-16', 'utf-16be'). Usage was minimal and support was removed from the spec. The TextEncoder constructor will no longer take an argument (if one is passed it is ignored, as is the standard for DOM APIs), and will always encode to "the encoding" (utf-8). #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder(Docs still refer to the utfLabel parameter, which is no longer supported.)
No linked samples