API Deprecations and Removals in Chrome 57
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 57, which is in beta as of early February. This list is subject to change at any time.
Deprecate case-insensitive matching for usemap attribute
The usemap attribute was formerly defined as caseless. Unfortunately
implementing this was complicated enough that no browsers implemented it
correctly. Research suggested that such complicated algorithm is unnecessary,
and even ASCII case-insensitive matching is unnecessary.
Consequently, the specification was updated so that case-sensitive matching is applied. The old behavior is deprecated in Chrome 57, with removal expected in Chrome 58.
Intent to Remove | Chromestatus Tracker | Chromium Bug
Deprecate and remove webkitCancelRequestAnimationFrame
The webkitCancelRequestAnimationFrame() method is a an obsolete,
vendor-specific API and the standard cancelAnimationFrame() has long
been supported in Chromium. Therefore the webkit version is being removed.
Intent to Remove | Chromestatus Tracker | Chromium Bug
Prefixed resource timing buffer-management API (removed)
Two methods and an event handler, webkitClearResourceTimings(),
webkitSetResourceTimingBufferSize(), and onwebkitresourcetimingbufferfull
are obsolete and vendor-specific. The
standard versions of these APIs
have been supported in since Chrome 46. These features were originally
implemented in WebKit, but Safari has not enabled them. Firefox, IE 10+, and
Edge have only unprefixed version of the API. Therefore the webkit versions
are being removed.
Intent to Remove | Chromestatus Tracker | Chromium Bug
Remove BluetoothDevice.uuids attribute
The BluetoothDevice.uuids attribute is being removed to bring the
Bluetooth API in
line with the current specification. You can retrieve a UUID by calling
device.watchAdvertisements().
Remove key generation element
Since Chrome 49, <keygen>'s default behaviour has been to return the empty
string, unless a permission was granted to this page. IE/Edge do not support
<keygen> and have not indicated public signals to support <keygen>.
Firefox already gates <keygen> behind a user gesture, but is publicly
supportive of removing it. Safari ships <keygen> and has not expressed
public views regarding its continued support. With Chrome 57, this element
is removed.
Intent to Remove | Chromestatus Tracker | Chromium Bug
Remove webkit-prefixed IndexedDB global aliases
The IndexedDB entry point and global constructors were exposed with webkit
prefixes somewhere around Chrome 11. The non-prefixed versions were added in
Chrome 24 and the prefixed versions were deprecated in Chrome 38. The
following interfaces are affected:
webkitIndexedDB(main entry point)webkitIDBKeyRange(non-callable global constructor, but has useful static methods)webkitIDBCursorwebkitIDBDatabasewebkitIDBFactorywebkitIDBIndexwebkitIDBObjectStorewebkitIDBRequestwebkitIDBTransaction(non-callable global constructors)
Intent to Remove | Chromestatus Tracker | Chromium Bug
WebAudio: Remove prefixed AudioContext and OfflineAudioContext
Chrome has supported WebAudio since mid 2011, including AudioContext.
OfflineAudioContext was added the following year. Given how long the
standard interfaces and Googles long-term goal of removing prefixed features,
the prefixed versions of these interfaces have been deprecated since late
2014 and are now being removed.
Intent to Remove | Chromestatus Tracker | Chromium Bug
<<../../_deprecation-policy.md>>