World Library  
Flag as Inappropriate
Email this Article

Add-on (Mozilla)

Article Id: WHEBN0001907070
Reproduction Date:

Title: Add-on (Mozilla)  
Author: World Heritage Encyclopedia
Language: English
Subject: History of Firefox, Mozilla, Ubiquity (Firefox), Firefox Sync, Jetpack (Firefox project)
Collection: Free Software Websites, Mozilla, Mozilla Add-Ons
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Add-on (Mozilla)

Firefox add-on manager, displaying a list of installed plug-ins

Mozilla add-ons are installable enhancements to the Mozilla Foundation's projects, including Firefox, Thunderbird, SeaMonkey, and Sunbird. Add-ons allow the user to add or augment application features, use themes to their liking, and handle new types of content.

There are three types of add-ons: "Extensions", "Personas" and "Plug-ins". The main repository for distributing the first two type is the eponymous Mozilla Add-ons website.

Contents

  • Types 1
  • Website 2
    • History 2.1
  • Extensions 3
    • Extension technologies 3.1
    • Uses 3.2
    • Security 3.3
    • Compatibility and updates 3.4
  • Themes 4
  • Plugins 5
  • References 6
  • External links 7

Types

There are several types of add-ons:

  • Extensions: Modify the behavior of existing features or add new features. The feature could be something in the user interface or a functional feature that manifests itself when a certain action is performed. Themes are examples of extensions that primarily concern themselves with the user interface. Search engine definitions are examples of functional extensions. A list of extensions can be found in the List of Firefox extensions article, although there are others for Thunderbird, SeaMonkey and Sunbird.
  • Themes: Formerly known as "Personas". Strictly modify certain elements of the user interface. Their most prominently featured change is the background image that they add to toolbars, menu bars and status bars of the main application window. They may change the text and background color as well.
  • Plug-ins: Render web contents that the program cannot natively render. For example, Adobe Flash Player is such a plug-in; it renders embedded Adobe Flash contents in web pages. The framework that enables creation of Mozilla plug-ins is called NPAPI. Mozilla plug-ins are being phased out; Mozilla plans to discontinue most plug-ins in Firefox by 2016.[1]

Website

Add-ons for Firefox
Screenshot of Mozilla Add-ons website
Web address .org.mozillaaddons
Commercial? No
Type of site
Extension hosting
Registration Free; only needed for developers or for special features
Owner Mozilla Foundation
Created by Andy McKay, Chris Howse, Gregory Koberger, Jeff Balogh, Jorge Villalobos (jorgev), Justin Scott (fligtar), Kumar McMillan, Matt Claypotch, Stephen Donner, Wil Clouser, et al.[2]
Current status Active

The eponymous Mozilla Add-ons website is the official Mozilla Foundation repository for add-ons of Mozilla software, including Mozilla Firefox, Mozilla Thunderbird, SeaMonkey, and Mozilla Sunbird. These add-ons include Mozilla extensions and personas, but not Mozilla plug-ins.

In contrast to end-users, not just software developers. Many Mozilla applications contain direct links to the website, and contain settings to poll for updates to the extensions and the application itself. Firefox 3 includes features for retrieving and displaying content from the website in the add-on manager.[3]

On January 30, 2008, it was announced that over 600 million add-ons had been downloaded from the site and that over 100 million add-ons automatically check the site for updates every day.[4]

On July 26, 2012, Mozilla announced that 3 billion add-ons were downloaded from the site.[5]

History

Formerly, Mozilla Add-ons was known as Mozilla Update (or UMO, as the

  • Official website
  • Extensions documentation on Mozilla Developer Center
  • Current Version Plugins of Mozilla

External links

  1. ^ Smedberg, Benjamin (8 October 2015). "NPAPI Plugins in Firefox". Future Releases.  
  2. ^ "Site Credits". Mozilla Add-ons. Mozilla Foundation. Retrieved 16 February 2011. 
  3. ^ "Customizing your Firefox with add-ons: Acquiring add-ons". Retrieved 2008-07-07. 
  4. ^ "600,000,000 Add-on Downloads < Blog of Metrics". Blog.Mozilla.com. 
  5. ^ "Firefox Add-ons Cross More Than 3 Billion Downloads!". The Mozilla blog. Retrieved 1 November 2013. 
  6. ^ "MozillaWiki: AMO Roadmap". Retrieved 2008-07-07. 
  7. ^ "MozillaWiki: Remora". Retrieved 2008-07-07. 
  8. ^ "Traces of a new AMO". 
  9. ^ "Previewing AMO's new look". 
  10. ^ Chapter 2: Technologies used in developing extensions - Firefox addons developer guide | MDN. Developer.mozilla.org. Retrieved on 2013-07-21.
  11. ^ User script - GreaseSpot Wiki. Wiki.greasespot.net (2010-11-17). Retrieved on 2013-07-21.
  12. ^ "Abusing, Exploiting and Pwning with Firefox Add-ons" (PDF). 
  13. ^ "Add-on code stored in profile folder raises security risk". 
  14. ^ Fisher, Dennis. "Firefox 40 Begins Warning Users About Unsigned Add-Ons". Threatpost. Retrieved 20 August 2015. 
  15. ^ "Extension Signing". Mozilla.org Wiki. Mozilla. Retrieved 20 August 2015. 
  16. ^ "Personas for Firefox: Getting Started".  
  17. ^ http://blog.mozilla.org/addons/2012/03/01/personas-are-joining-the-themes-family/
  18. ^ https://blog.mozilla.org/addons/2013/02/28/getpersonas-com-migration-update/
  19. ^ "Make Your Firefox Browser Look Better With Mozilla Labs' Latest Skins".  
  20. ^ "Check Your Plugins". mozilla.org.  
  21. ^ Smedberg, Benjamin (8 October 2015). "NPAPI Plugins in Firefox". Future Releases.  

References

Mozilla plug-ins are being phased out; Mozilla plans to discontinue most plug-ins in Firefox by 2016.[21]

Mozilla plugins are browser extensions used render web contents that the application itself cannot render. They are created using NPAPI framework. Firefox 41.0 comes with two plug-ins pre-installed: "Open H.264 Video Codec" by Cisco and "Primetime Content Decryption Module" by Adobe Systems. Common third-party Mozilla plugins include Adobe Flash Player, Acrobat Reader, Adobe Shockwave Player, Java SE, QuickTime and RealPlayer. Unlike other types of add-ons, Mozilla does not distribute plug-ins; furthermore the add-on manager cannot update them.[20]

Plugins

Although the feature was met with general favor, TechCrunch has criticized Mozilla for focusing on developing eye candy for the browser rather than placing more attention on improving the speed and usability of Firefox.[19]

Originally hosted on GetPersonas.com, they were moved to the Mozilla Add-ons website in 2013. In addition, because to the similarity of the name with an authentication scheme called "Mozilla Persona", Mozilla stopped using this term in favor the more generic word "theme", even though there is a distinction between theme implemented as an extension and Personas, in terms of installation and handling by Add-on Manager.[17][18]

Themes,[16] originally called Personas, allow users to quickly change the look of their applications. Although support for Personas was initially available as an extension, the feature was built into Firefox 3.6, and later other applications. These background themes differ from traditional themes available before, which were implemented as Mozilla extensions. Mozilla themes are more basic, easier to create, and easier to install, but are limited to changing the background image, background color and text color of toolbars, menu bars and status bars. They cannot alter the shape or appearance of toolbar items or tabs in the way that extensions can. In regards to installation, they can be installed and activated with exactly one click.

LibreOffice Writer using a persona

Themes

The add-on manager periodically checks for updates for extensions installed from the Mozilla Add-ons website, although checks for updates can be manually initiated by the user. If the developer includes provisions to check elsewhere, the add-on manager will do so.

Extensions contain XML files bearing metadata utilized by the mechanism which controls add-on installation. Among other things, this file identifies maximum and minimum versions of a Mozilla project application on which the add-on may be used. If an attempt is made to install the add-on on a version outside of this range, it will install but will be disabled. The success of a formal compatibility check is no guarantee the add-on will work, however. It is even possible to override the compatibility check using various extensions.

Compatibility and updates

From Firefox 40.0, Mozilla began to roll out a requirement for extension signing in the Release and Beta channels to improve end-user security. From 40.0, the browser warns the end user an extension is unsigned, from 43.0, unsigned extensions could only be installed if a special option in the about:config page was enabled. In 44.0 Firefox will block the installation of unsigned extensions. The Developer Edition and Nightly versions of Firefox will have a setting to disable signature enforcement. An unbranded version of Firefox Release and Beta is planned to allow developers to work on extensions without the requirement.[14][15]

Mozilla extensions are per default installed into the applications user profile where their code can be overwritten by the user or any program run by the user. Since the Mozilla platform does not check the integrity of installed extensions they can trivially be (ab)used for arbitrary code execution.[13]

Unlike Google Chrome, the Mozilla platform has no mechanism to restrict the privileges of extensions. Extension code is fully trusted by Mozilla applications. There are no restrictions on intercommunication between extensions as well as the operating system. This means that one extension can read or modify the data used by another extension or any file accessible to the user running Mozilla applications.[12]

Security

Extensions also exist for frivolous, humorous or satirical purposes. Some allude to historical features of the Firefox browser, for example restoring the "delicious delicacies" placeholder text removed in Firefox 0.9, or generating random browser names to allude to the Firefox name changes.

Modifying how the user views web pages
Many extensions can change the content of a webpage as it is rendered. For example, Adblock extensions can prevent the browser from loading images which are advertisements. Another popular extension, Greasemonkey, allows the user to install scripts which modify a targeted subset of webpages on the fly in a manner which is the programmatic complement to user style sheets.[11]
Adding features
Extensions are generally used to add functions to the application. Examples of functions which an extension might add include toolbars, website-specific client programs, FTP, e-mail, mouse gestures, proxy server switching, or developer tools. Many Firefox extensions implement features formerly part of the Mozilla Suite, such as the ChatZilla IRC client and a calendar.
Interface changes
Some extensions are used to change the interface of the application. These are not to be confused with personas, which are a theme management feature. For example, several add-ons exist to change the color of the Firefox button, such as ColorizedButton. There is also an add-on which moves the menu bar to where the window title normally is on windows machines.

Uses

Extensions can be developed using the following technologies:[10]

Extension technologies

Extensions can be used to modify the behavior of existing features to the application or add entirely new features. Extensions are especially popular with Firefox, because Mozilla developers intend for the browser to be a fairly minimalistic application in order to reduce software bloat and bugs, while retaining a high degree of extensibility, so that individual users can add the features that they prefer.

Extensions

  • A major rewrite of the public pages was launched on April 4, 2006.
  • A visual refresh of the Firefox pages was pushed on October 24, 2006 to correspond with the launch of Firefox 2 and the newly styled mozilla.com.
  • A complete rewrite of both the developer and public pages, codenamed Remora,[7] was launched on March 23, 2007.
  • Another visual refresh, "Remora 3.2", launched spring 2008.
  • In 2011, Remora (written in PHP/CakePHP) was replaced with Zamboni (written in Python/Django).[8] The site also featured a redesign,[9] codenamed Impala.

[6]

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.