JavaScript programming language: Final chance to drop early Web Components API before Chrome ditches support

Google will continue to support API v0 in Chrome until around February 2020 so that developers have more time to update.

Node.js JavaScript vs. PHP: What programming language is winning the developers?
A report highlights the growing popularity of Node.js JavaScript as a server-side language to support online sites and services.

Must: read Developer Content

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.

The Web Components API allows developers to use JavaScript to define custom reusable HTML tags to use on their site and is now compatible with all major browsers.

However, the web components started as an initiative of Google and in its first iteration, known as v0, the JavaScript API was only compatible with Chrome.

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 . .

For those who can not update at present, Google also provides an additional polyfill JavaScript code that allows Web Components v0 to work in browsers that do not support it.

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.

Developers using version 1 or 2 of Polymer, Google's JavaScript library to create web applications, will indirectly use v0 of web components, although they are likely not affected by the removal of support, due to the polymer cluster Polfill code to handle cases where the v0 API is not compatible.

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.

For more information on the popular JavaScript spin-off TypeScript language, read TechRepublic's summary of the best free resources to learn the language online.

See also

For More Updates Check out Blog, Windows Softwares Drivers, Antivirus, Ms Office, Graphic Design Don’t Forget to Look Our Facebook Page Get Into Pc like us & follow on Twitter- @getinpc

Please Note: This content is provided and hosted by a 3rd party server. Sometimes these servers may include advertisements. does not host or upload this material and is not responsible for the content.