This article needs to be updated.(February 2019) |
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 problems, 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.
During 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 since 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]
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 (support for XUL was removed in Firefox version 57). 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.
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:
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:
Most of the larger toolbar providers have a toolbar uninstaller or directions for how to remove their toolbars. [33] [34] [35] 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. [36]
The following is a list of web browser toolbar articles on Wikipedia:
Mozilla Firefox, or simply Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. It uses the Gecko rendering engine to display web pages, which implements current and anticipated web standards. In November 2017, Firefox began incorporating new technology under the code name "Quantum" to promote parallelism and a more intuitive user interface. Firefox is available for Windows 7 and later versions, macOS, and Linux. Its unofficial ports are available for various Unix and Unix-like operating systems, including FreeBSD, OpenBSD, NetBSD, illumos, and Solaris Unix. It is also available for Android and iOS. However, as with all other iOS web browsers, the iOS version uses the WebKit layout engine instead of Gecko due to platform requirements. An optimized version is also available on the Amazon Fire TV as one of the two main browsers available with Amazon's Silk Browser.
A browser war is competition for dominance in the usage share of web browsers. The "first browser war," (1995-2001) pitted Microsoft's Internet Explorer against Netscape's Navigator. Browser wars continued with the decline of Internet Explorer's market share and the popularity of other browsers including Firefox, Google Chrome, Safari, Microsoft Edge and Opera.
This is a comparison of both historical and current web browsers based on developer, engine, platform(s), releases, license, and cost.
Mozilla Firefox has features that allow it to be distinguished from other web browsers, such as Chrome and Internet Explorer.
Netscape Plugin Application Programming Interface (NPAPI) was an application programming interface (API) of the web browsers that allows plugins to be integrated.
A JavaScript engine is a software component that executes JavaScript code. The first JavaScript engines were mere interpreters, but all relevant modern engines use just-in-time compilation for improved performance.
DOM Inspector (DOMi) is a web developer tool created by Joe Hewitt and was originally included in Mozilla Application Suite as well as versions of Mozilla Firefox prior to Firefox 3. It is now included in Firefox, and SeaMonkey. Its main purpose is to inspect and edit the Document Object Model (DOM) tree of HTML and XML-based documents.
Add-on is the Mozilla term for software modules that can be added to the Firefox web browser and related applications. Mozilla hosts them on its official add-on website.
NoScript is a free and open-source extension for Firefox- and Chromium-based web browsers, written and maintained by Giorgio Maone, an Italian software developer and member of the Mozilla Security Group.
A browser extension is a small software module for customizing a web browser. Browsers typically allow a variety of extensions, including user interface modifications, cookie management, ad blocking, and the custom scripting and styling of web pages.
Firebug is a discontinued free and open-source web browser extension for Mozilla Firefox that facilitated the live debugging, editing, and monitoring of any website's CSS, HTML, DOM, XHR, and JavaScript.
Gears, formerly Google Gears, is discontinued utility software offered by Google to create more powerful web apps by adding offline storage and other additional features to web browsers. Released under the BSD license, Gears is free and open-source. Gears was conceived at a time when a comparable alternative was not available. However, Gears was discontinued in favor of the standardized HTML5 methods that eventually became prevalent.
Web development tools allow web developers to test and debug their source codes. They are different from website builders and integrated development environments (IDEs) in that they do not assist in the direct creation of a webpage, rather they are tools used for testing the user interface of a website or web application.
Internet Explorer 9 or IE9 is the ninth version of the Internet Explorer web browser for Windows. It was released by Microsoft on March 14, 2011, as the ninth version of Internet Explorer and the successor to Internet Explorer 8. Microsoft released Internet Explorer 9 as a major out-of-band version that was not tied to the release schedule of any particular version of Windows, unlike previous versions. It is the first version of Internet Explorer not to be bundled with a Windows operating system, although some OEMs have installed it with Windows 7 on their PCs. Internet Explorer 9 is the last version that is called Windows Internet Explorer. The software was rebranded simply as Internet Explorer starting in 2012 with the release of Internet Explorer 10.
Google Chrome is a cross-platform web browser developed by Google. It was first released in 2008 for Microsoft Windows, built with free software components from Apple WebKit and Mozilla Firefox. Versions were later released for Linux, macOS, iOS, and also for Android, where it is the default browser. The browser is also the main component of ChromeOS, where it serves as the platform for web applications.
Web Slices are a web feed technology based on the hAtom Microformat that allows users to subscribe to portions of a web page. Microsoft developed the Web Slice format, and published a specification under their Open Specification Promise. The specification is not published by any independent standards body. Introduced in Internet Explorer 8 Beta 1, Web Slices can be previewed in a fly-out window. As of 2012,, Internet Explorer 8 and 9 were the only browsers to support Web Slices natively, although Mozilla Firefox had support via an add-on called webchunks.
Web storage, sometimes known as DOM storage, is a standard JavaScript API provided by web browsers. It enables websites to store persistent data on users' devices similar to cookies, but with much larger capacity and no information sent in HTTP headers. There are two main web storage types: local storage and session storage, behaving similarly to persistent cookies and session cookies respectively. Web Storage is standardized by the World Wide Web Consortium (W3C) and WHATWG, and is supported by all major browsers.
WebGL is a JavaScript API for rendering interactive 2D and 3D graphics within any compatible web browser without the use of plug-ins. WebGL is fully integrated with other web standards, allowing GPU-accelerated usage of physics and image processing and effects as part of the web page canvas. WebGL elements can be mixed with other HTML elements and composited with other parts of the page or page background.
Content Security Policy (CSP) is a computer security standard introduced to prevent cross-site scripting (XSS), clickjacking and other code injection attacks resulting from execution of malicious content in the trusted web page context. It is a Candidate Recommendation of the W3C working group on Web Application Security, widely supported by modern web browsers. CSP provides a standard method for website owners to declare approved origins of content that browsers should be allowed to load on that website—covered types are JavaScript, CSS, HTML frames, web workers, fonts, images, embeddable objects such as Java applets, ActiveX, audio and video files, and other HTML5 features.
HTML5 Audio is a subject of the HTML5 specification, incorporating audio input, playback, and synthesis, as well as speech to text, in the browser.