Misplaced Pages

Browser extension: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 21:04, 1 September 2023 edit92.40.216.139 (talk)No edit summaryTags: Manual revert Reverted← Previous edit Latest revision as of 01:13, 13 October 2024 edit undoCitation bot (talk | contribs)Bots5,405,541 edits Added date. | Use this bot. Report bugs. | Suggested by Jay8g | #UCB_toolbar 
(65 intermediate revisions by 37 users not shown)
Line 1: Line 1:
{{short description|Program that extends the functionality of a web browser}} {{short description|Program that extends the functionality of a web browser}}
{{Use dmy dates|date=March 2024}}


A '''''' is a ] module for customizing a ]. Browsers typically allow users to install a variety of extensions, including ] modifications, ] management, ], and the custom ] and ] of ]s.<ref>{{Cite web|url=https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/What_are_WebExtensions|title=What are extensions?|website=MDN Web Docs|language=en|access-date=2019-08-05}}</ref> A '''browser extension''' is a ] module for customizing a ]. Browsers typically allow users to install a variety of extensions, including ] modifications, ] management, ], and the custom ] and ] of ]s.<ref>{{Cite web|url=https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/What_are_WebExtensions|title=What are extensions?|website=MDN Web Docs|language=en|access-date=2019-08-05}}</ref>


Browser ] are a different type of module and no longer supported by the major browsers.<ref name="mozwiki-plugin"/><ref>{{cite news |title=Why Browser Plug-Ins Are Going Away and What's Replacing Them |url=https://www.howtogeek.com/179213/why-browser-plug-ins-are-going-away-and-whats-replacing-them/ |access-date=6 June 2023 |publisher=howtogeek.com |date=8 January 2014}}</ref> One difference is that extensions are distributed as ], while plug-ins are ]s (i.e. ]).<ref name="mozwiki-plugin">{{Cite web |title=Plugin|url=https://developer.mozilla.org/en-US/docs/Glossary/Plugin|access-date=2022-12-07|website=developer.mozilla.org |date=9 September 2022 |language=en-US}}</ref> The most popular browser, ],<ref>{{cite web |title=StatCounter Global Stats |url=https://gs.statcounter.com/ |website=StatCounter |access-date=11 November 2020}}</ref> has over 100,000 extensions available<ref>{{Cite web|last=Cimpanu|first=Catalin|title=Half of all Google Chrome extensions have fewer than 16 installs|url=https://www.zdnet.com/article/half-of-all-google-chrome-extensions-have-fewer-than-16-installs/|access-date=2021-02-19|website=ZDNet|language=en}}</ref> but stopped supporting plug-ins in 2020.<ref>{{cite web |title=Google Chrome 88 released: RIP Flash Player |url=https://www.bleepingcomputer.com/news/google/google-chrome-88-released-rip-flash-player-and-ftp-support/ |access-date=29 January 2021}}</ref> Browser ] are a different type of module and no longer supported by the major browsers.<ref name="mozwiki-plugin"/><ref>{{cite news |title=Why Browser Plug-Ins Are Going Away and What's Replacing Them |url=https://www.howtogeek.com/179213/why-browser-plug-ins-are-going-away-and-whats-replacing-them/ |access-date=6 June 2023 |publisher=howtogeek.com |date=8 January 2014}}</ref> One difference is that extensions are distributed as ], while plug-ins are ]s (i.e. ]).<ref name="mozwiki-plugin">{{Cite web |title=Plugin|url=https://developer.mozilla.org/en-US/docs/Glossary/Plugin|access-date=2022-12-07|website=developer.mozilla.org |date=9 September 2022 |language=en-US}}</ref> The most popular browser, ],<ref name=statcounter>{{cite web |title=StatCounter Global Stats |url=https://gs.statcounter.com/ |website=StatCounter |access-date=11 November 2020}}</ref> has over 100,000 extensions available<ref>{{Cite web|last=Cimpanu|first=Catalin|title=Half of all Google Chrome extensions have fewer than 16 installs|url=https://www.zdnet.com/article/half-of-all-google-chrome-extensions-have-fewer-than-16-installs/|access-date=2021-02-19|website=ZDNet|language=en}}</ref> but stopped supporting plug-ins in 2020.<ref>{{cite web |title=Google Chrome 88 released: RIP Flash Player |url=https://www.bleepingcomputer.com/news/google/google-chrome-88-released-rip-flash-player-and-ftp-support/ |access-date=29 January 2021}}</ref>


==History== ==History==
] was the first major browser to support extensions, with the release of ] in 1999.<ref>{{cite web|title=Browser Extensions| date=15 August 2017 |url=https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa753620(v=vs.85)|access-date =2020-09-29}}</ref> ] has supported extensions since its launch in 2004. ] and Chrome began supporting extensions in 2009,<ref>{{Cite web |last1=Edwards |first1=Lin |last2=Phys.org |title=Google Chrome extensions to be officially released |url=https://phys.org/news/2009-12-google-chrome-extensions.html |access-date=2023-04-27 |website=phys.org |language=en}}</ref> and ] did so the following year. ] added extension support in 2016.<ref>{{cite web|last1=Bright|first1=Peter|title=Edge browser now has extensions in the latest Windows 10 preview|url=https://arstechnica.com/information-technology/2016/03/edge-browser-now-has-extensions-in-the-latest-windows-10-preview/|website=]|publisher=]|date=18 March 2016}}</ref> ] was the first major browser to support extensions, with the release of ] in 1997.<ref>{{cite web|title=Browser Extensions| date=15 August 2017 |url=https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa753620(v=vs.85)|access-date =2020-09-29}}</ref> ] has supported extensions since its launch in 2004. ] and Chrome began supporting extensions in 2009,<ref>{{Cite web |last1=Edwards |first1=Lin |last2=Phys.org |title=Google Chrome extensions to be officially released |url=https://phys.org/news/2009-12-google-chrome-extensions.html |access-date=2023-04-27 |website=phys.org |language=en}}</ref> and ] did so the following year. ] added extension support in 2016.<ref>{{cite web|last1=Bright|first1=Peter|title=Edge browser now has extensions in the latest Windows 10 preview|url=https://arstechnica.com/information-technology/2016/03/edge-browser-now-has-extensions-in-the-latest-windows-10-preview/|website=]|publisher=]|date=18 March 2016}}</ref>


===API conformity=== ===API conformity===
In 2015, a community working group formed under the ] to create a single standard ] (API) for browser extensions.<ref>{{Cite web|url=https://browserext.github.io/charter/|title=Browser Extension Community Group Charter — Browser Extension Community Group|website=browserext.github.io|access-date=2018-12-14}}</ref> While that goal is unlikely to be achieved,<ref>{{Cite web|url=https://lists.w3.org/Archives/Public/public-browserext/2017Jul/0001.html|title=Re: One question from Florian Rivoal on 2017-07-29 (public-browserext@w3.org from July 2017)|website=lists.w3.org|access-date=2018-12-14}}</ref> the majority of browsers already use the same or very similar APIs due to the popularity of ]. In 2015, a community group formed under the ] to create a single standard ] (API) for browser extensions.<ref>{{Cite web|url=https://browserext.github.io/charter/|title=Browser Extension Community Group Charter — Browser Extension Community Group|website=browserext.github.io|access-date=2018-12-14}}</ref> While this particular work did not reach fruition,<ref>{{Cite web|url=https://lists.w3.org/Archives/Public/public-browserext/2017Jul/0001.html|title=Re: One question from Florian Rivoal on 2017-07-29 (public-browserext@w3.org from July 2017)|website=lists.w3.org|access-date=2018-12-14}}</ref> every major browser now has the same or very similar API due to the popularity of ].<ref name=statcounter/>


Chrome was the first browser with an extension API based solely on ], ], and ]. Beta testing for this capability began in 2009,<ref>{{Cite web|url=https://blog.chromium.org/2009/09/extensions-status-on-runway-getting.html|title=Extensions Status: On the Runway, Getting Ready for Take-Off|website=Chromium Blog|language=en|access-date=2018-12-14}}</ref><ref>{{Cite web|url=https://blog.chromium.org/2009/12/extensions-beta-launched-with-over-300.html|title=Extensions beta launched, with over 300 extensions!|website=Chromium Blog|language=en|access-date=2018-12-14}}</ref> and the following year ] opened the ]. As of June 2012, there were 750 million total installations of extensions and other content hosted on the store.<ref>{{cite web|author=Vikas SN |url=http://www.medianama.com/2012/06/223-the-lowdown-google-io-2012-day-2-310m-chrome-users-425m-gmail-more/ |title=The Lowdown: Google I/O 2012 Day 2 – 310M Chrome Users, 425M Gmail & More |publisher=MediaNama |date=2012-06-29 |access-date=2013-06-14}}</ref> In the same year, Chrome overtook ] as the world's most popular browser,<ref>{{cite web |url=http://www.digitaltrends.com/web/internet-explorer-usage-to-plummet-below-50-percent-by-mid-2012/attachment/net-applications-browser-market/ |title=Internet Explorer usage to plummet below 50 percent by mid-2012 |date=3 September 2011 |access-date=4 September 2011 |archive-url=https://web.archive.org/web/20111120200340/http://www.digitaltrends.com/web/internet-explorer-usage-to-plummet-below-50-percent-by-mid-2012/attachment/net-applications-browser-market/ |archive-date=20 November 2011 |url-status=dead }}</ref> and its ] continued to grow, reaching 60% in 2018.<ref>{{Cite web|url=https://gs.statcounter.com/browser-market-share#monthly-201809-201809-bar|title=Browser Market Share Worldwide {{!}} StatCounter Global Stats|last=Statcounter|website=gs.statcounter.com|language=en|access-date=October 20, 2018}}</ref> Chrome was the first browser with an extension API based solely on ], ], and ]. Beta testing for this capability began in 2009,<ref>{{Cite web|url=https://blog.chromium.org/2009/09/extensions-status-on-runway-getting.html|title=Extensions Status: On the Runway, Getting Ready for Take-Off|website=Chromium Blog|language=en|access-date=2018-12-14}}</ref><ref>{{Cite web|url=https://blog.chromium.org/2009/12/extensions-beta-launched-with-over-300.html|title=Extensions beta launched, with over 300 extensions!|website=Chromium Blog|language=en|access-date=2018-12-14}}</ref> and the following year ] opened the ]. As of June 2012, there were 750 million total installations of extensions and other content hosted on the store.<ref>{{cite web|author=Vikas SN |url=http://www.medianama.com/2012/06/223-the-lowdown-google-io-2012-day-2-310m-chrome-users-425m-gmail-more/ |title=The Lowdown: Google I/O 2012 Day 2 – 310M Chrome Users, 425M Gmail & More |publisher=MediaNama |date=2012-06-29 |access-date=2013-06-14}}</ref> In the same year, Chrome overtook ] as the world's most popular browser,<ref>{{cite web |url=http://www.digitaltrends.com/web/internet-explorer-usage-to-plummet-below-50-percent-by-mid-2012/attachment/net-applications-browser-market/ |title=Internet Explorer usage to plummet below 50 percent by mid-2012 |date=3 September 2011 |access-date=4 September 2011 |archive-url=https://web.archive.org/web/20111120200340/http://www.digitaltrends.com/web/internet-explorer-usage-to-plummet-below-50-percent-by-mid-2012/attachment/net-applications-browser-market/ |archive-date=20 November 2011 |url-status=dead }}</ref> and its ] reached 60% in 2018.<ref>{{Cite web|url=https://gs.statcounter.com/browser-market-share#monthly-201809-201809-bar|title=Browser Market Share Worldwide {{!}} StatCounter Global Stats|last=Statcounter|website=gs.statcounter.com|language=en|access-date=October 20, 2018}}</ref>


Because of Chrome's success, ] created a very similar extension API for its ] browser, with the goal of making it easy for Chrome extension developers to port their work to Edge.<ref>{{cite web |title=Porting an extension from Chrome to Microsoft Edge |url=https://docs.microsoft.com/en-us/microsoft-edge/extensions/guides/porting-chrome-extensions |publisher=Microsoft |access-date=30 December 2018}}</ref> But after three years Edge still had a disappointingly small market share, so Microsoft rebuilt it as a ]-based browser.<ref>{{Cite web|url=https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/|title=Microsoft Edge: Making the web better through more open source collaboration|date=2018-12-06|website=Windows Experience Blog|language=en-US|access-date=2018-12-14}}</ref><ref name="computerworld">{{Cite web|url=https://www.computerworld.com/article/3325333/web-browsers/with-move-to-rebuild-edge-atop-googles-chromium-microsoft-raises-white-flag-in-browser-war.html|title=With move to rebuild Edge atop Google's Chromium, Microsoft raises white flag in browser war|last=Keizer|first=Gregg|date=2018-12-08|website=Computerworld|language=en|access-date=2018-12-14}}</ref> (Chromium is Google's open-source project that serves as the functional core of Chrome and ] browsers.) Now that Edge has the same API as Chrome, extensions can be installed directly from the Chrome Web Store.<ref>{{Cite web|url=https://support.microsoft.com/en-us/help/4538971/microsoft-edge-add-or-remove-extensions|title=Add or remove extensions in Microsoft Edge|website=Microsoft|language=en|access-date=2020-06-08}}</ref> Because of Chrome's success, ] created a very similar extension API for its ] browser, with the goal of making it easy for Chrome extension developers to port their work to Edge.<ref>{{cite web |title=Porting an extension from Chrome to Microsoft Edge |url=https://docs.microsoft.com/en-us/microsoft-edge/extensions/guides/porting-chrome-extensions |publisher=Microsoft |access-date=30 December 2018}}</ref> But after three years Edge still had a disappointingly small market share, so Microsoft rebuilt it as a ]-based browser.<ref>{{Cite web|url=https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/|title=Microsoft Edge: Making the web better through more open source collaboration|date=2018-12-06|website=Windows Experience Blog|language=en-US|access-date=2018-12-14}}</ref><ref name="computerworld">{{Cite web|url=https://www.computerworld.com/article/3325333/web-browsers/with-move-to-rebuild-edge-atop-googles-chromium-microsoft-raises-white-flag-in-browser-war.html|title=With move to rebuild Edge atop Google's Chromium, Microsoft raises white flag in browser war|last=Keizer|first=Gregg|date=2018-12-08|website=Computerworld|language=en|access-date=2018-12-14}}</ref> (Chromium is Google's open-source project that serves as the functional core of Chrome and ] browsers.) Now that Edge has the same API as Chrome, extensions can be installed directly from the Chrome Web Store.<ref>{{Cite web|url=https://support.microsoft.com/en-us/help/4538971/microsoft-edge-add-or-remove-extensions|title=Add or remove extensions in Microsoft Edge|website=Microsoft|language=en|access-date=2020-06-08}}</ref>


With its own market share in decline, ] also decided to conform. In 2015, the organization announced that the long-standing ] and ] extension capabilities of ] would be replaced with a less-permissive API very similar to Chrome's.<ref>{{Cite web|url=https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/|title=The Future of Developing Firefox Add-ons|website=Mozilla Add-ons Blog|date=21 August 2015 |language=en-US|access-date=2018-12-15}}</ref> This change was enacted in 2017.<ref>{{Cite web|url=https://blog.mozilla.org/addons/2017/08/10/upcoming-changes-compatibility/|title=Upcoming Changes in Compatibility Features|website=Mozilla Add-ons Blog|date=10 August 2017 |language=en-US|access-date=2018-12-15}}</ref><ref>{{Cite web|url=https://www.ghacks.net/2017/08/12/how-to-enable-legacy-extensions-in-firefox-57/|title=How to enable legacy extensions in Firefox 57 - gHacks Tech News|website=www.ghacks.net|date=12 August 2017|access-date=2018-12-14}}</ref> Firefox extensions are now largely compatible with their Chrome counterparts.<ref>{{cite web |title=Porting a Google Chrome extension |url=https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension |publisher=Mozilla |access-date=30 December 2018}}</ref> In 2015, ] announced that the long-standing ] and ] extension capabilities of ] would be replaced with a less-permissive API very similar to Chrome's.<ref>{{Cite web|url=https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/|title=The Future of Developing Firefox Add-ons|website=Mozilla Add-ons Blog|date=21 August 2015 |language=en-US|access-date=2018-12-15}}</ref> This change was enacted in 2017.<ref>{{Cite web|url=https://blog.mozilla.org/addons/2017/08/10/upcoming-changes-compatibility/|title=Upcoming Changes in Compatibility Features|website=Mozilla Add-ons Blog|date=10 August 2017 |language=en-US|access-date=2018-12-15}}</ref><ref>{{Cite web|url=https://www.ghacks.net/2017/08/12/how-to-enable-legacy-extensions-in-firefox-57/|title=How to enable legacy extensions in Firefox 57 - gHacks Tech News|website=www.ghacks.net|date=12 August 2017|access-date=2018-12-14}}</ref> Firefox extensions are now largely compatible with their Chrome counterparts.<ref>{{cite web |title=Porting a Google Chrome extension |url=https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension |publisher=Mozilla |access-date=30 December 2018}}</ref>


Until 2020, ] was the lone major exception to this trend, but with the release of Safari 14 for macOS, the browser added support for extensions conforming to the Chrome API.<ref>{{Cite web |date=2020 |title=Safari 14 Release Notes |url=https://developer.apple.com/documentation/safari-release-notes/safari-14-release-notes |url-status=live |archive-url=https://web.archive.org/web/20220323052246/https://developer.apple.com/documentation/safari-release-notes/safari-14-release-notes |archive-date=March 23, 2022 |access-date=April 4, 2022}}</ref> The following year, extensions were enabled in the iOS version for the first time.<ref>{{Cite web |last=Ortolani |first=Parker |date=2021-09-21 |title=Here are the best new Safari extensions to download for iOS 15 and iPadOS 15 (Updated) |url=https://9to5mac.com/2021/09/21/here-are-the-best-new-safari-extensions-to-download-for-ios-15-and-ipados-15/ |access-date=2022-04-05 |website=9to5Mac |language=en-US}}</ref> ] was the last major exception to this trend, but support for extensions conforming to the Chrome API was added to ] for ] in 2020.<ref>{{Cite web |date=2020 |title=Safari 14 Release Notes |url=https://developer.apple.com/documentation/safari-release-notes/safari-14-release-notes |url-status=live |archive-url=https://web.archive.org/web/20220323052246/https://developer.apple.com/documentation/safari-release-notes/safari-14-release-notes |archive-date=March 23, 2022 |access-date=April 4, 2022}}</ref> Extensions were later enabled in the ] version for the first time.<ref>{{Cite web |last=Ortolani |first=Parker |date=2021-09-21 |title=Here are the best new Safari extensions to download for iOS 15 and iPadOS 15 (Updated) |url=https://9to5mac.com/2021/09/21/here-are-the-best-new-safari-extensions-to-download-for-ios-15-and-ipados-15/ |access-date=2022-04-05 |website=9to5Mac |language=en-US}}</ref>

In 2021, these browser vendors formed a new W3C community group, called WebExtensions, to "specify a model, permissions, and a common core of APIs".<ref name="WECG home">{{cite web |title=WebExtensions Community Group |url=https://www.w3.org/community/webextensions/ |website=w3.org |date=3 April 2023 |access-date=24 March 2024}}</ref> However, Google joined this during its overhaul of Chrome's extension API, known as ], which greatly reduces the capability of ] and ]-related extensions.<ref>{{Cite web |last=Barnett |first=Daly |date=2021-12-09 |title=Chrome Users Beware: Manifest V3 is Deceitful and Threatening |url=https://www.eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening |access-date=2023-11-22 |website=]}}</ref><ref>{{Cite web |last=Amadeo |first=Ron |date=2023-12-01 |title=Chrome's next weapon in the War on Ad Blockers: Slower extension updates |url=https://arstechnica.com/google/2023/12/chromes-next-weapon-in-the-war-on-ad-blockers-slower-extension-updates/ |access-date=2023-12-02 |website=Ars Technica}}</ref><ref>{{Cite web |date=2023-12-01 |title=Inside the 'arms race' between YouTube and ad blockers |url=https://www.engadget.com/inside-the-arms-race-between-youtube-and-ad-blockers-140031824.html |access-date=2023-12-02 |website=Engadget}}</ref> Thus the WebExtensions group is viewed by some extension developers as nothing more than Google imposing its Manifest V3 design.<ref>{{cite web |last1=Stuwe |first1=Cuyler |title=Re: Do not outlaw dynamic code |url=https://github.com/w3c/webextensions/issues/139#issuecomment-1002880671 |website=] |quote=Nobody outside of Google really has any meaningful sway, since Chrome currently owns nearly all of the market share; Google sets the rules, other people nitpick minor details, and everyone pretends that everyone had a meaningful say. |date=29 December 2021}}</ref><ref>{{cite web |title=Re: Do not outlaw dynamic code |url=https://github.com/w3c/webextensions/issues/139#issuecomment-1003782643 |website=] |quote=Google has shown no interest whatsoever in deviating from their original plans. So, it's quite clear what's happening here. MV3 is a business decision, not an engineering decision. |date=2 January 2022}}</ref><ref>{{cite web |title=Re: Manifest v3 background scripts should not be killed when there are active listeners |url=https://github.com/w3c/webextensions/issues/518#issuecomment-1880189646 |website=] |date=7 January 2024}}</ref>


==Unwanted behavior== ==Unwanted behavior==

Latest revision as of 01:13, 13 October 2024

Program that extends the functionality of a web browser

A browser extension is a software module for customizing a web browser. Browsers typically allow users to install a variety of extensions, including user interface modifications, cookie management, ad blocking, and the custom scripting and styling of web pages.

Browser plug-ins are a different type of module and no longer supported by the major browsers. One difference is that extensions are distributed as source code, while plug-ins are executables (i.e. object code). The most popular browser, Google Chrome, has over 100,000 extensions available but stopped supporting plug-ins in 2020.

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

  1. "What are extensions?". MDN Web Docs. Retrieved 5 August 2019.
  2. ^ "Plugin". developer.mozilla.org. 9 September 2022. Retrieved 7 December 2022.
  3. "Why Browser Plug-Ins Are Going Away and What's Replacing Them". howtogeek.com. 8 January 2014. Retrieved 6 June 2023.
  4. ^ "StatCounter Global Stats". StatCounter. Retrieved 11 November 2020.
  5. Cimpanu, Catalin. "Half of all Google Chrome extensions have fewer than 16 installs". ZDNet. Retrieved 19 February 2021.
  6. "Google Chrome 88 released: RIP Flash Player". Retrieved 29 January 2021.
  7. "Browser Extensions". 15 August 2017. Retrieved 29 September 2020.
  8. Edwards, Lin; Phys.org. "Google Chrome extensions to be officially released". phys.org. Retrieved 27 April 2023.
  9. Bright, Peter (18 March 2016). "Edge browser now has extensions in the latest Windows 10 preview". Ars Technica. Condé Nast.
  10. "Browser Extension Community Group Charter — Browser Extension Community Group". browserext.github.io. Retrieved 14 December 2018.
  11. "Re: One question from Florian Rivoal on 2017-07-29 (public-browserext@w3.org from July 2017)". lists.w3.org. Retrieved 14 December 2018.
  12. "Extensions Status: On the Runway, Getting Ready for Take-Off". Chromium Blog. Retrieved 14 December 2018.
  13. "Extensions beta launched, with over 300 extensions!". Chromium Blog. Retrieved 14 December 2018.
  14. Vikas SN (29 June 2012). "The Lowdown: Google I/O 2012 Day 2 – 310M Chrome Users, 425M Gmail & More". MediaNama. Retrieved 14 June 2013.
  15. "Internet Explorer usage to plummet below 50 percent by mid-2012". 3 September 2011. Archived from the original on 20 November 2011. Retrieved 4 September 2011.
  16. Statcounter. "Browser Market Share Worldwide | StatCounter Global Stats". gs.statcounter.com. Retrieved 20 October 2018.
  17. "Porting an extension from Chrome to Microsoft Edge". Microsoft. Retrieved 30 December 2018.
  18. "Microsoft Edge: Making the web better through more open source collaboration". Windows Experience Blog. 6 December 2018. Retrieved 14 December 2018.
  19. Keizer, Gregg (8 December 2018). "With move to rebuild Edge atop Google's Chromium, Microsoft raises white flag in browser war". Computerworld. Retrieved 14 December 2018.
  20. "Add or remove extensions in Microsoft Edge". Microsoft. Retrieved 8 June 2020.
  21. "The Future of Developing Firefox Add-ons". Mozilla Add-ons Blog. 21 August 2015. Retrieved 15 December 2018.
  22. "Upcoming Changes in Compatibility Features". Mozilla Add-ons Blog. 10 August 2017. Retrieved 15 December 2018.
  23. "How to enable legacy extensions in Firefox 57 - gHacks Tech News". www.ghacks.net. 12 August 2017. Retrieved 14 December 2018.
  24. "Porting a Google Chrome extension". Mozilla. Retrieved 30 December 2018.
  25. "Safari 14 Release Notes". 2020. Archived from the original on 23 March 2022. Retrieved 4 April 2022.
  26. Ortolani, Parker (21 September 2021). "Here are the best new Safari extensions to download for iOS 15 and iPadOS 15 (Updated)". 9to5Mac. Retrieved 5 April 2022.
  27. "WebExtensions Community Group". w3.org. 3 April 2023. Retrieved 24 March 2024.
  28. Barnett, Daly (9 December 2021). "Chrome Users Beware: Manifest V3 is Deceitful and Threatening". Electronic Frontier Foundation. Retrieved 22 November 2023.
  29. Amadeo, Ron (1 December 2023). "Chrome's next weapon in the War on Ad Blockers: Slower extension updates". Ars Technica. Retrieved 2 December 2023.
  30. "Inside the 'arms race' between YouTube and ad blockers". Engadget. 1 December 2023. Retrieved 2 December 2023.
  31. Stuwe, Cuyler (29 December 2021). "Re: Do not outlaw dynamic code". GitHub. Nobody outside of Google really has any meaningful sway, since Chrome currently owns nearly all of the market share; Google sets the rules, other people nitpick minor details, and everyone pretends that everyone had a meaningful say.
  32. "Re: Do not outlaw dynamic code". GitHub. 2 January 2022. Google has shown no interest whatsoever in deviating from their original plans. So, it's quite clear what's happening here. MV3 is a business decision, not an engineering decision.
  33. "Re: Manifest v3 background scripts should not be killed when there are active listeners". GitHub. 7 January 2024.
  34. "Protect User Privacy". Google Chrome Docs. 18 March 2018. Retrieved 15 December 2018.
  35. "Add-on Policies". MDN Web Docs. Retrieved 15 December 2018.
  36. "Security firm ICEBRG uncovers 4 malicious Chrome extensions - gHacks Tech News". www.ghacks.net. 16 January 2018. Retrieved 15 December 2018.
  37. "Google's bad track record of malicious Chrome extensions continues - gHacks Tech News". www.ghacks.net. 11 May 2018. Retrieved 15 December 2018.
  38. "Chrome Extension Devs Use Sneaky Landing Pages after Google Bans Inline Installs". BleepingComputer. Retrieved 15 December 2018.
  39. "Google Chrome extensions with 500,000 downloads found to be malicious". Ars Technica. 17 January 2018. Retrieved 30 December 2018.
  40. "PUP Criteria". Malwarebytes. Retrieved 13 February 2015.
  41. "Adware vendors buy Chrome Extensions to send ad- and malware-filled updates". Ars Technica. 17 January 2014. Retrieved 20 January 2014.
  42. Bruce Schneier (21 January 2014). "Adware Vendors Buy and Abuse Chrome Extensions".
  43. Winkler, Rolfe (19 January 2014). "Google Removes Two Chrome Extensions Amid Ad Uproar". blogs.wsj.com. Wall Street Journal. Retrieved 17 March 2014.
  44. "Ad Injection at Scale: Assessing Deceptive Advertisement Modifications" (PDF). Archived from the original (PDF) on 5 June 2015.
  45. "Superfish injects ads into 5 percent of all Google page views". PC World. IDG.
  46. "Superfish injects ads in one in 25 Google page views". CIO. IDG. Archived from the original on 11 December 2019. Retrieved 16 June 2015.

External links

Web browsers
  • Features
  • standards
  • protocols
Features
Web standards
Protocols
Active
Blink-based
Proprietary
FOSS
Gecko-based
WebKit-based
Multi-engine
Other
Discontinued
Blink-based
Gecko-based
MSHTML-based
WebKit-based
Other
Web interfaces
Server-side
Protocols
Server APIs
Apache modules
Topics
Client-side
Browser APIs
Web APIs
WHATWG
W3C
Khronos
Others
Topics
Related topics
Categories: