Add-ons/Terminology: Difference between revisions

Jump to navigation Jump to search
m
→‎Glossary: clarification on deprecation
m (more examples)
m (→‎Glossary: clarification on deprecation)
Line 11: Line 11:
*'''Extensions:''' pieces of code that extend the capabilities of a browser. In Firefox, extensions are a type of add-on.
*'''Extensions:''' pieces of code that extend the capabilities of a browser. In Firefox, extensions are a type of add-on.
*'''Browser extensions:''' cross-browser extensions implemented using the [https://browserext.github.io/ Browser Extensions standard]. ([https://www.smashingmagazine.com/2017/04/browser-extension-edge-chrome-firefox-opera-brave-vivaldi/ This article] illustrates it nicely).
*'''Browser extensions:''' cross-browser extensions implemented using the [https://browserext.github.io/ Browser Extensions standard]. ([https://www.smashingmagazine.com/2017/04/browser-extension-edge-chrome-firefox-opera-brave-vivaldi/ This article] illustrates it nicely).
*'''WebExtensions:''' a deprecated term that describes Firefox extensions built with WebExtensions APIs. Starting in Firefox 57, only extensions built with WebExtensions APIs will be supported. Therefore, we will start referring to them simply as "extensions". "WebExtensions" will remain in use in context of describing the underlying technology (see below).
*'''WebExtensions:''' as a standalone noun, this is a deprecated term that used to describe an extension built using WebExtensions APIs. With WebExtensions APIs becoming the only supported API in Firefox 57, we are simply calling them "extensions." [[Add-ons/Terminology#Usage_Guidelines|See below]] on how "WebExtensions" can still be used as a standalone adjective.
*'''Legacy extensions:''' Firefox extensions built using legacy APIs or the Add-on SDK.
*'''Legacy extensions:''' Firefox extensions built using legacy APIs or the Add-on SDK.


Confirmed users
1,605

edits

Navigation menu