Don't miss out on the action at this year's Chrome Dev Summit, streaming live on YouTube. Watch now.

Deprecations and Removals in Chrome 62

In nearly every version of Chrome, we see a significant number of updates and improvements to the product, its performance, and also capabilities of the Web Platform. This article describes the deprecations and removals in Chrome 62, which is in beta as of September 14. This list is subject to change at any time.

Remove RTCPeerConnection.getStreamById()

Nearly two years ago, getStreamById() was removed from the WebRTC spec. Most other browsers have already removed this from their implementations, and the feature was deprecated in Chrome 60. Though this function is believed to be little-used, it's also believed there is some minor interoperability risk with Edge and WebKit-based browsers other than Safari where getStreamById() is still supported. Developers needing an alternative implementation can find example code in the Intent to Remove, below.

Intent to Remove | Chromestatus Tracker | Chromium Bug

Remove SharedWorker.workerStart

This property, which was intended for use in monitoring worker performance was removed from the spec more than two years ago and it is not supported in the other major browsers. A more modern approach to tracking performance of a worker would use Performance.timing.

Intent to Remove | Chromestatus Tracker | Chromium Bug

Remove SVGPathElement.getPathSegAtLength()

In Chrome 48, SVGPathElement.pathSegList() and related interfaces were removed in compliance with the SVG specification. At that time, this method was mistakenly left in. We don't excpct this removal to break any web pages since, for the last two years, it has returned an object that no longer exists in Blink.

Intent to Remove | Chromestatus Tracker | Chromium Bug

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.