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 9 new features.
Language support for classes. In 42, shipped in strict mode. In 49, shipped outside of strict mode as well. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/classes-es6
Allows concise methods and property shorthands in object literals #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer
No linked samplesDefines a common API that may be used to discover, select and interact with Digital Rights Management systems for use with HTMLMediaElement. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/EncryptedMediaExtensions_API
Samples: https://shaka-player-demo.appspot.com/
Fetch API is a new API for loading resources in web applications. It's intended to supersede XMLHttpRequest. Fetch API is already available in ServiceWorker scope. This entry is for announcing its availability in window scope. #
This feature was specified in this Spec.
Docs: http://updates.html5rocks.com/2015/03/introduction-to-fetchhttps://developer.mozilla.org/en-US/docs/Web/API/Fetch_API
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/fetch-api
Instantiate new ImageData objects by way of an object constructor. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en/docs/Web/API/ImageData
No linked samplesWeb Notifications have an in-page event delivery model by default, which means that notifications cannot reliably outlive the page's lifetime. Allowing event delivery to be routed to a page's Service Worker provides a solid solution. #
This feature was specified in this Spec.
Docs: http://updates.html5rocks.com/2015/03/push-notificatons-on-the-open-web
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/push-messaging-and-notifications
Push notifications for the web #
This feature was specified in this Spec.
Docs: http://updates.html5rocks.com/2015/03/push-notificatons-on-the-open-webhttps://developer.mozilla.org/en-US/docs/Web/API/Push_API
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/push-messaging-and-notifications
Chrome 42 for Android will encourage users to add high quality sites they visit frequently to their home screen. In the future it will support the same for native apps. This entry is for the visual aspect, not the API surface. The Manifest API surface is covered by https://www.chromestatus.com/features/4754986680451072. The event API surface is covered in https://www.chromestatus.com/features/6560913322672128 #
This feature was specified in this Spec.
Docs: https://github.com/slightlyoff/AppInstallImprovements/blob/master/explainer.mdhttp://updates.html5rocks.com/2015/03/increasing-engagement-with-app-install-banners-in-chrome-for-android
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/app-install-banner/
The startRendering() method for an OfflineAudioContext now returns a promise that is resolved with the rendered audio when rendering is done. #
This feature was specified in this Spec.
Docs: http://webaudio.github.io/web-audio-api/#widl-OfflineAudioContext-startRendering-Promise-AudioBuffer
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/webaudio-offlinecontext-rendering
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.
Setting AudioBufferSourceNode.buffer more than once is deprecated. A deprecation message is displayed if the buffer attribute is assigned more than once. #
This feature was specified in this Spec.
Docs: https://github.com/WebAudio/web-audio-api/issues/288
No linked samplesThis release of Chrome had 1 features removed.
The global showModalDialog() method displays a modal dialog box containing a specified HTML document. This feature has an incredibly high cost in terms of code complexity since it requires us to run an event loop on top of an arbitrary JavaScript stack. It also complicates the web platform by making task dispatch reentrant and hard to reason about. In Chrome 37 it was disabled and in Chrome 43 it is removed. #
This feature was specified in this Spec.
Docs: http://blog.chromium.org/2014/07/disabling-showmodaldialog.htmlhttp://dev.opera.com/blog/showmodaldialog/
No linked samples