Google will continue to support API v0 in Chrome until around February 2020 so that developers have more time to update.
Web developers who are still using the previous version of the Google Web Components API on their sites have been granted a suspension of execution.
In an attempt to encourage developers to move to the browser's cross-browser v1 API, Google planned to remove support for the v0 API with the release of Chrome 73, in May.
SEE: How to build a successful developer career (free PDF)
But Google did not remove the support for the API to give them more time to update, and now says it will continue with the v0 API until the launch of Chrome 80, around February 2020.
"Because enough developers requested more time to migrate, the APIs have not yet been removed from Chrome," writes the Google web developers team.
Google has published a series of guides for web developers that want to verify if their site would be affected by the elimination of support for API v0, which includes instructions on how to disable support for API v0 to see how the site works . .
If developers are not sure if they are using an outdated version of the web components API, they can open the DevTools console by pressing Ctrl + Shift + J (Cmd + Shift + J on Mac) in Chrome and verifying messages that begin with "[Deprecation]", which will detail the APIs whose support should be removed.
"The v0 draft web APIs are going to go. If you remove anything from this post, be sure to test your application with the v0 APIs disabled and load the polyfills as needed," writes the Google team.
Web components are an increasingly popular way for web developers to reuse code for features such as custom user interfaces on web pages and applications, with millions of sites using version 1 of the web components API.