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 55, which is in beta as of October 21. This list is subject to change at any time.
Resources with non-script MIME types can no longer be executed
Previous versions of Chrome allowed content to with several non-script
to be executed as script. In addition to the obvious security vulnerability,
this problem also reduces the value of
content security policy
The implementation of
SVGSVGElement.viewPort has not worked in
since 2012. The attribute is not present at all in other browsers and
it has been removed from the specification. For these reasons the property was
deprecated in Chrome 54 and has now been removed.
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, or 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 that if needed, they can make the required changes to keep their sites running.
Chrome currently has a process for deprecations and removals of API's and the TL;DR is:
- Announce on the blink-dev mailing list.
- Set warnings and give time scales in the Chrome DevTools Console when usage is detected on a page.
- Wait, monitor, and then remove feature as usage drops.
You can find a list of all deprecated features in 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. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.