Update "Overview of Microsoft Edge extensions"#3768
Conversation
|
Learn Build status updates of commit 8767faa: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 7ccae29: ✅ Validation status: passed
For more details, please refer to the build report. |
mikehoffms
left a comment
There was a problem hiding this comment.
LGTM - Writer/Editor
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit a933606: ✅ Validation status: passed
For more details, please refer to the build report. |
| * [See also](#see-also) | ||
| * [Microsoft Edge](#microsoft-edge) | ||
| * [Store](#store) | ||
| * [End-user docs](#end-user-docs) | ||
| * [Development](#development) | ||
| * [Google Chrome, or Chromium browser engine](#google-chrome-or-chromium-browser-engine) | ||
| * [Store](#store-1) | ||
| * [Development](#development-1) | ||
| * [Opera](#opera) | ||
| * [Store](#store-2) | ||
| * [Development](#development-2) | ||
| * [Brave](#brave) | ||
| * [Store](#store-3) | ||
| * [End-user docs](#end-user-docs-1) | ||
| * [Development](#development-3) | ||
| * [Apple Safari](#apple-safari) | ||
| * [Store](#store-4) | ||
| * [Development](#development-4) | ||
| * [Mozilla Firefox](#mozilla-firefox) | ||
| * [Store](#store-5) | ||
| * [Development](#development-5) | ||
| * [Non-browser extensions](#non-browser-extensions) |
There was a problem hiding this comment.
Could we make an exception and not display the detailed headings for the See also section?
These headings take a lot of space, as well as attention away from the more useful headings above.
| You can create a Microsoft Edge extension if you have an idea or product that is based upon either a specific web browser, or improvements to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers. | ||
|
|
||
| This article focuses mostly on Chromium-based extensions. |
There was a problem hiding this comment.
This section is making things unnecessarily high level, as if we're documenting how to build extensions in all browsers. We're not.
| You can create a Microsoft Edge extension if you have an idea or product that is based upon either a specific web browser, or improvements to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers. | |
| This article focuses mostly on Chromium-based extensions. | |
| You can create a Microsoft Edge extension to add features to the browser or improve to features of specific webpages. Examples of _companion experiences_ include ad blockers and password managers. |
| In the **Search extensions, themes, and more** text box, you can enter various search terms, such as the extension owner [Microsoft Corporation](https://microsoftedge.microsoft.com/addons/search/microsoft%20corporation). Searching returns extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension: | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
I suggest moving this up to line 60, just after we've introduced the "store", and slightly rephrase to make it clearer what we mean by Search extensions, themes, and more:
| In the **Search extensions, themes, and more** text box, you can enter various search terms, such as the extension owner [Microsoft Corporation](https://microsoftedge.microsoft.com/addons/search/microsoft%20corporation). Searching returns extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension: | |
|  | |
|  | |
| On the Microsoft Edge Add-ons site, you can enter various search terms in the **Search extensions, themes, and more** text box to find extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension: | |
|  |
| * A JavaScript file that defines the function. | ||
| * HTML and CSS files that define the user interface. | ||
|
|
||
| To work directly with a specific part of the browser, such as a window or tab, you must send API requests, and must often reference the browser by name. |
There was a problem hiding this comment.
I don't think this line is necessary. It's pretty high level and vague at this point in the article, and doesn't bring anything very concrete and useful to developers.
| ## Benefits of Chromium-based extensions | ||
|
|
||
| If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications. | ||
| If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari app extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications. |
There was a problem hiding this comment.
| If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. For example, [Safari app extensions](https://developer.apple.com/documentation/safariservices/safari_app_extensions) can use both web and native code to communicate with counterpart native applications. | |
| If your goal is to publish your extension in the extensions store for each browser, your extension must be modified for each version to target and run in each distinct browser environment. |
| The following browsers are based on the [Chromium](https://www.chromium.org/Home) open-source browser project: | ||
| * Microsoft Edge | ||
| * Google Chrome | ||
| * Opera | ||
| * Brave |
There was a problem hiding this comment.
Let's not be definitive. There are other browsers. And the list can change quickly.
| The following browsers are based on the [Chromium](https://www.chromium.org/Home) open-source browser project: | |
| * Microsoft Edge | |
| * Google Chrome | |
| * Opera | |
| * Brave | |
| Microsoft Edge is based on the [Chromium](https://www.chromium.org/Home) open-source browser project. Other browsers are also based on Chromium, such as Google Chrome, Opera, and Brave. |
| Chromium-based browsers use the same code package, and minimize the need to maintain parallel versions. | ||
|
|
||
| Benefits of creating a Chromium extension: | ||
| * Enables writing the fewest lines of code. | ||
| * Enables targeting the maximum number of extension stores and the maximum number of users who can find and acquire your extension. |
There was a problem hiding this comment.
| Chromium-based browsers use the same code package, and minimize the need to maintain parallel versions. | |
| Benefits of creating a Chromium extension: | |
| * Enables writing the fewest lines of code. | |
| * Enables targeting the maximum number of extension stores and the maximum number of users who can find and acquire your extension. | |
| Chromium-based browsers use the same extension APIs and way to package extensions, which minimizes the need to maintain parallel versions. | |
| By writing a Chromium extension, you write fewer lines of code and target more browsers. |
| * [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) | ||
| * [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) | ||
| * [Opera addons](https://addons.opera.com/extensions) | ||
| * [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) - store for Brave extensions. |
There was a problem hiding this comment.
We should remove this line. Even if it's for Brave, it's the same site as for Chrome.
| * [Apple App Store](https://apps.apple.com) | ||
| * [Firefox Browser Add-ons](https://addons.mozilla.org/firefox/extensions) | ||
|
|
||
| Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store. |
There was a problem hiding this comment.
Let's bring it back to Edge here. It's useful that the article mentions other browsers and other stores, but devs are here to build an Edge extension.
| Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store. | |
| Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store. | |
| To make sure your users find your extensions in Microsoft Edge, publish your extension on the Microsoft Edge Add-ons site. See [Publish an extension at Microsoft Edge Add-ons](#publish-an-extension-at-microsoft-edge-add-ons). |
| #### Non-browser extensions | ||
|
|
||
| * [Microsoft Edge DevTools extension for Visual Studio Code](../visual-studio-code/microsoft-edge-devtools-extension.md)<!-- link not in article --> | ||
| * [webhint extension for Visual Studio Code](../visual-studio-code/webhint.md)<!-- link not in article --> |
There was a problem hiding this comment.
I suggest removing these links. They're not related to browser extensions.
Rendered article sections for review:
/extensions/index.mdAB#60823027