Chrome 44

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

Enabled by default in 44

This release of Chrome had 7 new features.

Cache.add()

add() takes a RequestInfo object, fetches it and adds the response object into this Cache object. #

This feature was specified in this Spec.

Resources

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

No linked samples

Computed Property Names (ES6)

Allows expression for property names in object literals and class literals #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer#Computed_property_names

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/computed-properties-es6

Document.scrollingElement

Simple API to indicate whether 'body' or 'documentElement' is used for scrolling. Used to ease transition to spec-compliant scrolling behavior. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/document/scrollingElementhttps://dev.opera.com/articles/fixing-the-scrolltop-bug/

No linked samples

Fetch API: Request.context

Request.context contains the context of the Request, such as "fetch", "image", "script", "frame", etc. #

This feature was specified in this Spec.

Resources

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

No linked samples

Notification.data and ServiceWorkerRegistration.getNotifications()

Support for the Notification.data attribute, which allows authors to attach some (immutable) data to a persistent Web Notification they are displaying. Support for the static ServiceWorkerRegistration.getNotifications() method for getting all existing persistent notifications created by the current origin. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/notification/datahttps://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerRegistration/getNotifications

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/push-messaging-and-notifications

WebAudio: AudioBufferSourceNode.detune

Add ‘detune’ feature to AudioBufferSourceNode for the sample-accurate pitch control of sample playback. #

This feature was specified in this Spec.

Resources

Docs: https://github.com/WebAudio/web-audio-api/issues/333https://github.com/WebAudio/web-audio-api/issues/497

No linked samples

WebAudio: ChannelMergerNode Static Routing

This is to change the behavior of ChannelMergerNode when the input changes dynamically. There have been critical issues with the previous implementation. (See related issues for the detail) To address these issues, a new proposal for the ChannelMergerNode was made. The proposal effectively makes the channel order in the merger node static after the instantiation. #

This feature was specified in this Spec.

Resources

Docs: https://github.com/WebAudio/web-audio-api/issues/304crbug.com/441451https://github.com/WebAudio/web-audio-api/issues/459crbug.com/442925https://github.com/WebAudio/web-audio-api/issues/304#issuecomment-69641498

No linked samples

Origin Trials in-progress in 44

This release of Chrome had 0 new origin trials.

Flagged features in 44

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

Parsing related_applications from Web Manifest

We will start parsing the related_applications key in the web manifest to display install banners as described in https://www.chromestatus.com/features/4540065577435136 https://github.com/slightlyoff/AppInstallImprovements/blob/master/explainer.md#offering-related-applications (see open pull request on the manifest spec: https://github.com/w3c/manifest/pull/344) #

This feature was specified in this Spec.

Resources

Docs: https://github.com/w3c/manifest/issues/326https://github.com/w3c/manifest/pull/344

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:

• They are superseded by newer APIs.
• They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
• They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.

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:

• Announce on the blink-dev mailing list.
• Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
• Wait, monitor, and then remove the feature as usage drops.

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 44

This release of Chrome had 0 features deprecated.

Removed features in 44

This release of Chrome had 1 features removed.

WebAudio: Disallow setting AudioBufferSourceNode.buffer more than once

Setting AudioBufferSourceNode.buffer again after it has already been set to a non-null buffer is no longer allowed and will generate an exception. This feature was deprecated and is now being removed #

This feature was specified in this Spec.

Resources

Docs: https://github.com/WebAudio/web-audio-api/issues/288https://developer.mozilla.org/en-US/docs/Web/API/AudioBufferSourceNode/buffer

No linked samples