Confirmed users
1,605
edits
Add-ons/Terminology: Difference between revisions
Jump to navigation
Jump to search
m
clarification
m (→Glossary: clarification on deprecation) |
m (clarification) |
||
| Line 19: | Line 19: | ||
**'''Extensions''' add new features and functionality to browsers. Use "extensions" when talking about the type of add-on that adds new features and functionality to Firefox, or when talking about the customization of browsers in general. | **'''Extensions''' add new features and functionality to browsers. Use "extensions" when talking about the type of add-on that adds new features and functionality to Firefox, or when talking about the customization of browsers in general. | ||
*'''"WebExtensions" refers to the technology, and not extensions built with the technology''' - For example, “Cool new extensions” rather than “Cool new WebExtensions” | *'''"WebExtensions" refers to the technology, and not extensions built with the technology''' - For example, “Cool new extensions” rather than “Cool new WebExtensions” | ||
*'''"WebExtensions" can still be used as a standalone term''' - It is ok to use the word "WebExtension(s)" without "API" following it, as long as you are describing | *'''"WebExtensions" can still be used as a standalone term''' - It is ok to use the word "WebExtension(s)" without "API" following it, as long as you are describing the technology. For example: | ||
**To distinguish from a legacy extension: "Your WebExtension add-on displays a 'compatible with Firefox 57+' banner." | **To distinguish from a legacy extension: "Your WebExtension add-on displays a 'compatible with Firefox 57+' banner." | ||
**To describe the new system: "We're moving to a WebExtensions model for add-on development." | **To describe the new system: "We're moving to a WebExtensions model for add-on development." | ||