Chrome 69 also removed the
stalled event from
find the explanation in Audio/Video Updates in Chrome
69 by François Beaufort.
Removal of document.createTouchList()
TouchEvent() constructor has been
supported in Chrome
since version 48. To comply with the specification,
is now removed. The
document.createTouch() method was removed in Chrome 68.
The window.confirm() method no longer activates its parent tab
window.confirm() on a background tab will no longer activate that
tab. If it is called on a background tab, the function returns immediately with
false and no dialog box is shown to the user. If the tab is active, the call
behaves as usual.
window.alert() method was abused by sites for years, allowing them to
force themselves to the front, disrupting whatever the user was doing. There
was a similar problem with
window.prompt(). Because these behaviors were
removed in Chrome 64, and 56 respectively, the abuse has been moving to
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.