Browser extension

History

Internet Explorer was the first major browser to support extensions, with the release of version 4 in 1997. Firefox has supported extensions since its launch in 2004. Opera and Chrome began supporting extensions in 2009, and Safari did so the following year. Microsoft Edge added extension support in 2016.

API conformity

In 2015, a community group formed under the W3C to create a single standard application programming interface (API) for browser extensions. While this particular work did not reach fruition, every major browser now has the same or very similar API due to the popularity of Google Chrome.

Chrome was the first browser with an extension API based solely on HTML, CSS, and JavaScript. Beta testing for this capability began in 2009, and the following year Google opened the Chrome Web Store. As of June 2012, there were 750 million total installations of extensions and other content hosted on the store. In the same year, Chrome overtook Internet Explorer as the world's most popular browser, and its usage share reached 60% in 2018.

Because of Chrome's success, Microsoft created a very similar extension API for its Edge browser, with the goal of making it easy for Chrome extension developers to port their work to Edge. But after three years Edge still had a disappointingly small market share, so Microsoft rebuilt it as a Chromium-based browser. (Chromium is Google's open-source project that serves as the functional core of Chrome and many other browsers.) Now that Edge has the same API as Chrome, extensions can be installed directly from the Chrome Web Store.

In 2015, Mozilla announced that the long-standing XUL and XPCOM extension capabilities of Firefox would be replaced with a less-permissive API very similar to Chrome's. This change was enacted in 2017. Firefox extensions are now largely compatible with their Chrome counterparts.

Apple was the last major exception to this trend, but support for extensions conforming to the Chrome API was added to Safari for macOS in 2020. Extensions were later enabled in the iOS version for the first time.

In 2021, these browser vendors formed a new W3C community group, called WebExtensions, to "specify a model, permissions, and a common core of APIs". However, Google joined this during its overhaul of Chrome's extension API, known as Manifest V3, which greatly reduces the capability of ad blockers and privacy-related extensions. Thus the WebExtensions group is viewed by some extension developers as nothing more than Google imposing its Manifest V3 design.

Unwanted behavior

Browser extensions typically have access to sensitive data, such as browsing history, and they have the ability to alter some browser settings, add user interface items, or replace website content. As a result, there have been instances of malware, so users need to be cautious about what extensions they install.

There have also been cases of applications installing browser extensions without the user's knowledge, making it hard for the user to uninstall the unwanted extension.

Some Google Chrome extension developers have sold their extensions to third-parties who then incorporated adware. In 2014, Google removed two such extensions from the Chrome Web Store after many users complained about unwanted pop-up ads. The following year, Google acknowledged that about five percent of visits to its own websites had been altered by extensions with adware.

References

References

1. "What are extensions?".
2. (8 January 2014). "Why Browser Plug-Ins Are Going Away and What's Replacing Them". howtogeek.com.
3. (9 September 2022). "Plugin".
4. "StatCounter Global Stats".
5. "Chrome extension statistics (Jan 2026)".
6. "Google Chrome 88 released: RIP Flash Player".
7. (15 August 2017). "Browser Extensions".
8. "Google Chrome extensions to be officially released".
9. (18 March 2016). "Edge browser now has extensions in the latest Windows 10 preview". [[Condé Nast]].
10. "Browser Extension Community Group Charter — Browser Extension Community Group".
11. "Re: One question from Florian Rivoal on 2017-07-29 (public-browserext@w3.org from July 2017)".
12. (2024-11-21). "Build a cross-browser extension - Mozilla {{!}} MDN".
13. "Extensions Status: On the Runway, Getting Ready for Take-Off".
14. "Extensions beta launched, with over 300 extensions!".
15. Vikas SN. (2012-06-29). "The Lowdown: Google I/O 2012 Day 2 – 310M Chrome Users, 425M Gmail & More". MediaNama.
16. (3 September 2011). "Internet Explorer usage to plummet below 50 percent by mid-2012".
17. Statcounter. "Browser Market Share Worldwide {{!}} StatCounter Global Stats".
18. "Porting an extension from Chrome to Microsoft Edge". Microsoft.
19. (2018-12-06). "Microsoft Edge: Making the web better through more open source collaboration".
20. Keizer, Gregg. (2018-12-08). "With move to rebuild Edge atop Google's Chromium, Microsoft raises white flag in browser war".
21. "Add or remove extensions in Microsoft Edge".
22. (21 August 2015). "The Future of Developing Firefox Add-ons".
23. (10 August 2017). "Upcoming Changes in Compatibility Features".
24. (12 August 2017). "How to enable legacy extensions in Firefox 57 - gHacks Tech News".
25. "Porting a Google Chrome extension". Mozilla.
26. (2020). "Safari 14 Release Notes".
27. Ortolani, Parker. (2021-09-21). "Here are the best new Safari extensions to download for iOS 15 and iPadOS 15 (Updated)".
28. (3 April 2023). "WebExtensions Community Group".
29. Barnett, Daly. (2021-12-09). "Chrome Users Beware: Manifest V3 is Deceitful and Threatening".
30. Amadeo, Ron. (2023-12-01). "Chrome's next weapon in the War on Ad Blockers: Slower extension updates".
31. (2023-12-01). "Inside the 'arms race' between YouTube and ad blockers".
32. (29 December 2021). "Re: Do not outlaw dynamic code".
33. (2 January 2022). "Re: Do not outlaw dynamic code".
34. (7 January 2024). "Re: Manifest v3 background scripts should not be killed when there are active listeners".
35. (18 March 2018). "Protect User Privacy".
36. "Add-on Policies".
37. (16 January 2018). "Security firm ICEBRG uncovers 4 malicious Chrome extensions - gHacks Tech News".
38. (11 May 2018). "Google's bad track record of malicious Chrome extensions continues - gHacks Tech News".
39. "Chrome Extension Devs Use Sneaky Landing Pages after Google Bans Inline Installs".
40. (17 January 2018). "Google Chrome extensions with 500,000 downloads found to be malicious". Ars Technica.
41. "PUP Criteria". Malwarebytes.
42. (17 January 2014). "Adware vendors buy Chrome Extensions to send ad- and malware-filled updates". Ars Technica.
43. Bruce Schneier. (21 Jan 2014). "Adware Vendors Buy and Abuse Chrome Extensions".
44. Winkler, Rolfe. (19 January 2014). "Google Removes Two Chrome Extensions Amid Ad Uproar". Wall Street Journal.
45. "Ad Injection at Scale: Assessing Deceptive Advertisement Modifications".
46. "Superfish injects ads into 5 percent of all Google page views". [[IDG]].
47. "Superfish injects ads in one in 25 Google page views". [[IDG]].