It is quite challenging to create and manage browser add-ons that is supposed to support several. Although other browsers namely Firefox, Edge, and Opera have already introduce browser extension on Chrome’s API. Besides this, every bowser individually incorporates new functionalities and not necessarily adopt Google API’s updates.
Nevertheless, several browsers including Microsoft, Apple, Mozilla, and Google are joining hands to form a WebExtensions Community organization that strives to normalize APIs and its features in all participating browsers.
In a recent update, W3C confirmed the launch of The WebExtensions Community Group (WECG). The building base of this community group is being contributed by Apple, Mozilla, Microsoft, Google, and Apple. However these browsers have officially declared that other browser creators, extension planners, and those who wanted to potentially grow are also welcome to take part.
The community group can smoothly build the foundation by providing a uniform base of capabilities, APIs, and licenses. The normalization and uniformity of APIs will approach the structural path that net capacity building is based on. Browsers won’t be compelled to ignore proprietary features or APIs.
According to the blog post, every other browser developer will have to function their browser individually and have to manage their extension marketplace in the form of technology, reviewing, and editing reforms.
Chrome’s extension API has been calling out by the word WebExtensions for several years. Opera consider this name in 2013 when it got transitioned into Chrome-based browser. Similarly, in 2017, Firefox following Opera shifted to API. Meanwhile, Safari browser is the last one to access APIs support in 2020.
After accessing the support, every browser is allowed to standardize the functionality in accordance to their choice as the standardization process now enables the browser developers to do so. The permitted APIs and licenses are variable at larger extent for every browser. Vivaldi and the Microsoft Edge latest version are the chromium-based browsers and have a support of Chrome’s API with slight changes.
WebExtensions Community Group's (WECG) challenge is to make it easier for developers to construct extensions. To achieve this, participating browser vendors must use this community to provide a consistent performance model, APIs, and permissions. WECG also intends to improve the overall stability of extensions by laying out a system that is both efficient and safe.
Whereas the availability of a single WebExtensions Platform API is desirable, the organization believes that certain initiatives are beyond its competence.
Photo: Koshiro K/Shutterstock.com
Read next: The New Google Chrome 91 Update Has Enhanced Safe Browsing Features that Will Warn You Before You Install Untrusted Extensions And Suspicious Files
Nevertheless, several browsers including Microsoft, Apple, Mozilla, and Google are joining hands to form a WebExtensions Community organization that strives to normalize APIs and its features in all participating browsers.
In a recent update, W3C confirmed the launch of The WebExtensions Community Group (WECG). The building base of this community group is being contributed by Apple, Mozilla, Microsoft, Google, and Apple. However these browsers have officially declared that other browser creators, extension planners, and those who wanted to potentially grow are also welcome to take part.
The community group can smoothly build the foundation by providing a uniform base of capabilities, APIs, and licenses. The normalization and uniformity of APIs will approach the structural path that net capacity building is based on. Browsers won’t be compelled to ignore proprietary features or APIs.
According to the blog post, every other browser developer will have to function their browser individually and have to manage their extension marketplace in the form of technology, reviewing, and editing reforms.
Chrome’s extension API has been calling out by the word WebExtensions for several years. Opera consider this name in 2013 when it got transitioned into Chrome-based browser. Similarly, in 2017, Firefox following Opera shifted to API. Meanwhile, Safari browser is the last one to access APIs support in 2020.
After accessing the support, every browser is allowed to standardize the functionality in accordance to their choice as the standardization process now enables the browser developers to do so. The permitted APIs and licenses are variable at larger extent for every browser. Vivaldi and the Microsoft Edge latest version are the chromium-based browsers and have a support of Chrome’s API with slight changes.
WebExtensions Community Group's (WECG) challenge is to make it easier for developers to construct extensions. To achieve this, participating browser vendors must use this community to provide a consistent performance model, APIs, and permissions. WECG also intends to improve the overall stability of extensions by laying out a system that is both efficient and safe.
Whereas the availability of a single WebExtensions Platform API is desirable, the organization believes that certain initiatives are beyond its competence.
Photo: Koshiro K/Shutterstock.comRead next: The New Google Chrome 91 Update Has Enhanced Safe Browsing Features that Will Warn You Before You Install Untrusted Extensions And Suspicious Files
