WebExtensions
WebExtensions is a term that refers to a group of similar application programming interfaces (APIs) for browser extensions.
Google Chrome was the first web browser to have this type of extension API. Mozilla eventually developed its own imitation API for Firefox, but the other browsers considered part of the group are Chromium-based and thus can easily maintain API parity with Chrome.
Mozilla coined the WebExtensions name for its Firefox API, but did so to emphasize cross-browser compatibility and encourages the use of the term to refer to the group of similar APIs.[1][2]
History
Google Chrome was the first browser with an extension API based solely on HTML, CSS, and JavaScript. Beta testing for this extension capability began in 2009,[3][4] and the following year Google opened the Chrome Web Store. As of June 2012, there were 750 million total installs of extensions and other content hosted on the store.[5]
Microsoft debuted its Edge browser in 2014 with an extension API similar to Chrome's. This was a marked change from Internet Explorer extensions. In December 2018, Microsoft announced that Edge is being rebuilt as a Chromium-based browser.[6][7] One of the reasons is to have the same extension API as Chrome which should enable users to install extensions directly from the Chrome Web Store.[7][8]
In 2015, Mozilla announced that the long-standing XUL and XPCOM extension capabilities of Firefox would be replaced with a less-permissive API similar to Chrome's.[9] This change was enacted in 2017 with the release of Firefox 57.[10][11]
Attempts to create a single standard API have been unsuccessful. In 2015, the World Wide Web Consortium formed a working group to facilitate this,[12] but it is unlikely to achieve its goal.[13]
Malware
The APIs require extensions to list the types of browser settings and data that will be accessed.[14] This can include sensitive data, such as browsing history, or the ability to replace website content.[14][15] As a result, there have been instances of malware, so users need to be cautious about what extensions they install.[16][17][18]
References
- ^ Mozilla wiki
- ^ Mozilla WebExtensions homepage
- ^ "Extensions Status: On the Runway, Getting Ready for Take-Off". Chromium Blog. Retrieved 2018-12-14.
- ^ "Extensions beta launched, with over 300 extensions!". Chromium Blog. Retrieved 2018-12-14.
- ^ Vikas SN (2012-06-29). "The Lowdown: Google I/O 2012 Day 2 – 310M Chrome Users, 425M Gmail & More". MediaNama. Retrieved 2013-06-14.
- ^ "Microsoft Edge: Making the web better through more open source collaboration". Windows Experience Blog. 2018-12-06. Retrieved 2018-12-14.
- ^ a b Keizer, Gregg (2018-12-08). "With move to rebuild Edge atop Google's Chromium, Microsoft raises white flag in browser war". Computerworld. Retrieved 2018-12-14.
- ^ "r/Windows10 - Microsoft Edge: Making the web better through more open source collaboration". reddit. Retrieved 2018-12-15.
- ^ "The Future of Developing Firefox Add-ons". Mozilla Add-ons Blog. Retrieved 2018-12-15.
- ^ "Upcoming Changes in Compatibility Features". Mozilla Add-ons Blog. Retrieved 2018-12-15.
- ^ "How to enable legacy extensions in Firefox 57 - gHacks Tech News". www.ghacks.net. Retrieved 2018-12-14.
- ^ "Browser Extension Community Group Charter — Browser Extension Community Group". browserext.github.io. Retrieved 2018-12-14.
- ^ "Re: One question from Florian Rivoal on 2017-07-29 (public-browserext@w3.org from July 2017)". lists.w3.org. Retrieved 2018-12-14.
- ^ a b "Protect User Privacy". Google Chrome Docs. Retrieved 2018-12-15.
- ^ "Add-on Policies". MDN Web Docs. Retrieved 2018-12-15.
- ^ "Security firm ICEBRG uncovers 4 malicious Chrome extensions - gHacks Tech News". www.ghacks.net. Retrieved 2018-12-15.
- ^ "Google's bad track record of malicious Chrome extensions continues - gHacks Tech News". www.ghacks.net. Retrieved 2018-12-15.
- ^ "Chrome Extension Devs Use Sneaky Landing Pages after Google Bans Inline Installs". BleepingComputer. Retrieved 2018-12-15.