Browser toolbar

A browser toolbar is a toolbar that resides within a browser's window. All major web browsers provide support to browser toolbar development as a way to extend the browser's GUI and functionality. Browser toolbars are considered to be a particular kind of browser extensions that present a toolbar. Browser toolbars are specific to each browser, which means that a toolbar working on a browser does not work on another one. All browser toolbars must be installed in the corresponding browser before they can be used, and require updates when new versions are released.

Many high profile browser toolbars released over the years have been fraught with issues, either intentionally as malware or injected with computer viruses or due to poor or conflicting programming when considering multiple toolbars being included on the single browser.

Controversy

Over the 2000s, there was a proliferation of browser add-ons produced and released by a variety of software companies, both large and small, which were designed to extend the browsing experience for the end user. Due to this popularity, and the ease with which users could have these installed, there was additionally an adoption by malware, adware and other privacy-invasive tracking tools. The popularity of browser toolbars has declined.[1][2]

Many unscrupulous companies use software bundling to force users downloading one program to also install a browser toolbar, some of which invade the user's privacy by tracking their web history and search history online. Many antivirus companies refer to these programs as grayware or Potentially Unwanted Programs (PUPs).[3][4][5][6]

Developing a toolbar

The programming language and development tools behind a browser toolbar vary from one browser to another.

In Internet Explorer 5 or later toolbars may be created as browser extensions written in C# or C++. More specifically, it is possible to create up to three different kinds of toolbars (custom explorer bars, tool bands and desk bands[7]) and to combine them with browser helper objects in order to provide added functionality.

In Firefox toolbars can be created as add-ons that contribute to the GUI by extending the browser with XUL. The logic behind the toolbar is written in JavaScript running under expanded privileges.[8] Mozilla Jetpack[9] can be used to simplify the development of add-ons for Firefox.

In Safari 5 or later[10] toolbars can be created as extensions[11] that add bars[12] and buttons.[13] The logic behind the toolbar is written in JavaScript with access to a special JavaScript API[14] to interact with the Safari application and web content.

In Google Chrome 4 or later[15] toolbars can be created as extensions[16] that add browser actions[17] to the browser window. The logic behind the toolbar is written in JavaScript with access to a special JavaScript API[18] to interact with the Chrome application and web content. The privileges under which a Chrome extension runs are governed by a set of permissions.[19]

In Opera 11 or later[20] toolbars can be created as extensions[21] that add buttons[22] to the browser window. The logic behind the toolbar is written in JavaScript with access to a special JavaScript API[23] to interact with the Opera application and web content.

In Firefox, Chrome, Safari and Opera toolbar styling is done though CSS.

Native vs. injected toolbars

Some major browsers (Internet Explorer and Firefox) enable the creation of native toolbars i.e., toolbars which are directly inserted in the browser window. Examples of native toolbars are Google Toolbar[24] and Stumbleupon Toolbar.[25] Native toolbars use browser-specific code to create the same toolbar for each different browser version.

Some toolbar developers use a different approach and make the browser extension inject a JavaScript file in every web page visited by the user. All major browsers support injected toolbars. The code in this file inserts the toolbar as a part of the DOM in every web page. Injected toolbars use essentially the same JavaScript code to draw the toolbar for each different browser version.

Each approach has advantages and disadvantages for the different stakeholders.

From the user's perspective:

From the developer's perspective:

From the toolbar owner's perspective:

Cross-browser toolbar development

Another way to simplify the task of developing a toolbar for different browsers is to rely on a cross-browser extension development framework. Some of the most important frameworks are listed below:

Removing a browser toolbar

Most of the larger toolbar providers have a toolbar uninstaller or directions for how to remove their toolbars.[35][36][37] This process varies by browser type, version, OS, and toolbar provider.

Some toolbar providers do not give detailed instructions on how to remove their toolbars. Many 2nd tier providers and software bundled browser toolbars can be difficult to remove without a 3rd party toolbar removal utility.[38]

List

The following is a list of web browser toolbar articles on Wikipedia:

References

  1. "Toolbars WAR". Videohelp.host.sk. Retrieved 2014-02-26.
  2. Larry Seltzer (2009-02-10). "Enough with the Browser Toolbars Already". eWeek. Retrieved 2014-02-26.
  3. Vincentas (11 July 2013). "Grayware in SpyWareLoop.com". Spyware Loop. Retrieved 28 July 2013.
  4. "Threat Encyclopedia – Generic Grayware". Trend Micro. Retrieved 27 November 2012.
  5. "Rating the best anti-malware solutions". Arstechnica. Retrieved 28 January 2014.
  6. "PUP Criteria". https://www.malwarebytes.org/pup/. Malwarebytes. External link in |website= (help);
  7. "Different kinds of Internet Explorer toolbars". Msdn.microsoft.com. Retrieved 2014-02-26.
  8. Javascript running under expanded privileges
  9. "Mozilla Jetpack". Wiki.mozilla.org. 2014-02-05. Retrieved 2014-02-26.
  10. "Safari Release 5". Prnewswire.com. Retrieved 2014-02-26.
  11. "Safari Extension Developer Guide". Developer.apple.com. Retrieved 2014-02-26.
  12. "Safari extension bars". Developer.apple.com. Retrieved 2014-02-26.
  13. "Safari extension buttons". Developer.apple.com. Retrieved 2014-02-26.
  14. "Special JavaScript API from Safari's Extension Reference Guide". Developer.apple.com. Retrieved 2014-02-26.
  15. Baum, Nick (2010-01-25). "Google Chrome Release 4". Chrome.blogspot.com.es. Retrieved 2014-02-26.
  16. Google Chrome Extensions
  17. Browser Actions in Google Chrome
  18. Special JavaScript API from Google Chrome's Extension Reference Guide
  19. Google Chrome Extension Permissions
  20. "Opera Release 11". Opera.com. Retrieved 2014-02-26.
  21. "Opera Extensions". Dev.opera.com. 2011-06-21. Retrieved 2014-02-26.
  22. Software, Opera. "Browser Buttons in Opera". Dev.opera.com. Archived from the original on 2012-01-13. Retrieved 2014-02-26.
  23. "Special JavaScript API from Opera's Extension Reference Guide". Dev.opera.com. 2012-08-24. Archived from the original on 2012-03-04. Retrieved 2014-02-26.
  24. "Google Toolbar". Google.com. Retrieved 2014-02-26.
  25. "Stumbleupon Toolbar". Stumbleupon.com. Retrieved 2014-02-26.
  26. "Toolbar Studio". Besttoolbars.net. Retrieved 2014-02-26.
  27. "Neobars". Macte! Labs. Retrieved 2015-02-01.
  28. "Add-ons Framework". Besttoolbars.net. Retrieved 2014-02-26.
  29. Phil Windley and Q Wade Billings. "Kynetx". Kynetx. Retrieved 2014-02-26.
  30. "CrossRider". CrossRider. Retrieved 2014-02-26.
  31. "KangoExtensions". KangoExtensions. Retrieved 2014-02-26.
  32. "Conduit". Toolbar.conduit.com. Retrieved 2014-02-26.
  33. "Widdit". Widdit. 2012-10-13. Retrieved 2014-02-26.
  34. "ExtensionMaker". ToolbarDev.
  35. Toolbar. "Removing a Google Toolbar". Support.google.com. Retrieved 2014-02-26.
  36. Removing a Yahoo Toolbar
  37. "Removing a Bing Toolbar". Onlinehelp.microsoft.com. Retrieved 2014-02-26.
  38. "Universal Toolbar Removal Utility". Skipity.com. Retrieved 2014-02-26.
This article is issued from Wikipedia - version of the Sunday, January 24, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.