Chrome Release Summary

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

Chrome 43

Enabled (15) | Origin Trial (0) | Behind a flag (1) | Deprecated (0) | Removed (1)

Enabled by default in 43

This release of Chrome had 15 new features.

Allow JS-triggered copy/cut with a user gesture

execCommand("copy") and execCommand("cut") should be allowed to modify the system clipboard in the context of a user gesture (the spec uses the language "allowed to show a popup"). #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/document.execCommandhttp://updates.html5rocks.com/2015/04/cut-and-copy-commands

Samples: http://jsbin.com/yanamebope/quiethttps://github.com/GoogleChrome/samples/tree/gh-pages/cut-and-copy

CSSOM Document.elementsFromPoint API

An API on Document for returning the sequence of elements under a point. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/document/elementsFromPoint

No linked samples

Cache API (global scope)

The Cache API allows authors to fully and conveniently manage their content caches for offline use. An origin can have multiple, named Cache objects. This API is already available in a Service Worker context. This entry is to make it available globally (=> accessible from a document context). #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/Cachehttps://developer.mozilla.org/en-US/docs/Web/API/CacheStorage

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/service-worker/window-caches

Fetch API: Streaming response body

Addition of the response.body property to the Fetch API. response.body is a ReadableStream from the Streams Standard. #

This feature was specified in this Spec.

Resources

Docs: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/35_QSL1ABTYhttps://streams.spec.whatwg.org/#rshttps://developer.mozilla.org/en-US/docs/Web/API/Fetch_API

Samples: https://googlechrome.github.io/samples/fetch-api/fetch-response-stream.html

MouseEvent.buttons

The 'buttons' property on MouseEvent indicates (for ALL mouse events) which combination of buttons are current down. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/buttons

No linked samples

Move DOM attributes to prototype chains.

Blink has placed DOM attributes on instances instead of prototypes. However, the Web IDL spec requires that DOM attributes must be placed on prototype chains (except for a few exceptions such as static attributes and [Unforgeable].) We move DOM attributes on instances to prototype chains following the spec. #

This feature was specified in this Spec.

Resources

Docs: http://updates.html5rocks.com/2015/04/DOM-attributes-now-on-the-prototype

No linked samples

Permissions API

The Permissions API allows a web application to be aware of the status of a given permission, to know whether it is granted, denied or if the user will be asked whether the permission should be granted. The purpose of the API is to improve general UX with regards to permissions on the Web, allowing developers to be aware of what is going to happen will enable better flow. #

This feature was specified in this Spec.

Resources

Docs: http://updates.html5rocks.com/2015/04/permissions-api-for-the-webhttps://developer.mozilla.org/en-US/docs/Web/API/Permissions_API

Samples: https://googlechrome.github.io/samples/permissions/index.html

Remove designMode inheritance from ancestors

Change the initial value of document.designMode from "inherit" to "off" and remove support for "inherit". #

This feature was specified in this Spec.

Unprefixed CSS Animations

CSS Animations without the -webkit- prefix. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Using_CSS_animations

Samples: https://jsfiddle.net/cm1yrqy2/3/embedded/result/

Upgrade insecure requests

We encourage authors to transition their sites and applications away from insecure transport, and onto encrypted and authenticated connections, but mixed content checking causes headaches. This feature allows authors to ask the user agent to transparently upgrade HTTP resources to HTTPS to ease the migration burden. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/Security/CSP/CSP_policy_directives#upgrade-insecure-requests

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/csp-upgrade-insecure-requests

Web MIDI API

Defines an API supporting the MIDI protocol, enabling web applications to enumerate and select MIDI input and output devices on the client system and send and receive MIDI messages. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/MIDIAccesshttps://developer.mozilla.org/en-US/docs/Web/API/MIDIConnectionEventhttps://developer.mozilla.org/en-US/docs/Web/API/MIDIInput

No linked samples

WebAudio: Allow developers to close an AudioContext explicitly

An AudioContext can now be explicitly closed, thereby releasing any hardware resources associated with the AudioContext. Without this, developers had to depend on garbage collection of the AudioContext to release hardware resources. #

This feature was specified in this Spec.

Resources

Docs: http://webaudio.github.io/web-audio-api/#widl-AudioContext-close-Promise;https://developer.mozilla.org/en-US/docs/Web/API/AudioContext/close

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/webaudio-audiocontext-close

WebAudio: AudioBuffer copyFromChannel and copyToChannel

Support the copyFromChannel and copyToChannel methods on a WebAudio AudioBuffer #

This feature was specified in this Spec.

Resources

Docs: http://webaudio.github.io/web-audio-api/#widl-AudioBuffer-copyFromChannel-void-Float32Array-destination-long-channelNumber-unsigned-long-startInChannelhttp://webaudio.github.io/web-audio-api/#widl-AudioBuffer-copyToChannel-void-Float32Array-source-long-channelNumber-unsigned-long-startInChannelhttps://developer.mozilla.org/en-US/docs/Web/API/AudioBuffer/copyFromChannelhttps://developer.mozilla.org/en-US/docs/Web/API/AudioBuffer/copyToChannel

No linked samples

WebAudio: Selective Disconnection on AudioNode.disconnect()

Currently AudioNode.disconnect() disconnects all existing connections from output(s) of the AudioNode. This is to support disconnecting only one connection. There have been numerous requests to support selective disconnection with disconnect() method and Audio WG agreed to change the spec to accommodate the feature request. With this change, it is possible to disconnect a signal path out of multiple connections to AudioNode input or AudioParam. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/AudioNode/disconnect

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/webaudio-audionode-disconnect

autocapitalize

Enables web pages to give hint with regards to the autocapitalization behaviour to use on text fields. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/autocapitalize

Origin Trials in-progress in 43

This release of Chrome had 0 new origin trials.

Flagged features in 43

This release of Chrome had 1 are available behind a flag.

CSS font-size-adjust

The font-size-adjust CSS property specifies that font size should be chosen based on the height of lowercase letters rather than the height of capital letters. It was once dropped since css 2.1, but newly defined in CSS3 font. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/font-size-adjust

No linked samples

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:

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.

Deprecated features in 43

This release of Chrome had 0 features deprecated.

Removed features in 43

This release of Chrome had 1 features removed.

overflowchanged event

The overflowchanged event and the OverflowEvent interface have been removed. #

This feature was specified in this Spec.

Resources

Docs: http://trevorbrindle.com/chrome-43-broke-sencha/

No linked samples