Chrome Release Summary

Chrome version: 132, 131, 130, 129, 128, 127, 126, 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 39

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

Enabled by default in 39

This release of Chrome had 5 new features.

Beacon

This specification defines an interoperable means for site developers to asynchronously transfer small HTTP data from the User Agent to a web server. Initiated by the navigator.sendBeacon() method, the 'beacon' data will be transmitted by the User Agent as soon as possible, but independent of document navigation. The sendBeacon method returns true if the user agent is able to successfully queue the data for transfer. Otherwise it returns false. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeaconhttp://updates.html5rocks.com/2014/10/Send-beacon-data-in-Chrome-39

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

Generators (ES6)

A generator is a special type of function that works as a factory for iterators. #

This feature was specified in this Spec.

Resources

Docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Generatorhttp://updates.html5rocks.com/2014/10/Generators-the-Gnarly-Bits

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

Web Animations Javascript API [playback control]

A unified model for supporting animation and synchronization on the Web platform. This feature covers playback control of AnimationPlayer: play(), pause(), reverse(), finish(), currentTime, startTime, playbackRate and playState. #

This feature was specified in this Spec.

Resources

Docs: http://updates.html5rocks.com/2014/05/Web-Animations---element-animate-is-now-in-Chrome-36

Samples: http://web-animations.github.io

Web Application Manifest

This specification defines a JSON-based manifest, which provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when the user launches the web application. The manifest also allows developers to declare a default orientation for their web application, as well as how the application is to be displayed by the user agent (e.g. in fullscreen). #

This feature was specified in this Spec.

Resources

Docs: https://developers.google.com/web/fundamentals/web-app-manifest/https://developer.mozilla.org/en-US/docs/Web/Manifest

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/web-application-manifest

meta-theme-color

The meta-theme-color is the color of the brand, browser may use it when a distinct color representation is needed. #

This feature was specified in this Spec.

Resources

Docs: http://updates.html5rocks.com/2014/11/Support-for-theme-color-in-Chrome-39-for-Android

Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/web-application-manifest

Origin Trials in-progress in 39

This release of Chrome had 0 new origin trials.

Flagged features in 39

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

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 39

This release of Chrome had 0 features deprecated.

Removed features in 39

This release of Chrome had 0 features removed.