Skip to content

Commit ae3b511

Browse files
authored
Merge pull request #3651 from MicrosoftDocs/main
main to live - Nov. 24, 2025
2 parents b5fce49 + 01892b9 commit ae3b511

File tree

13 files changed

+222
-105
lines changed

13 files changed

+222
-105
lines changed

microsoft-edge/extensions/contact.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.date: 05/30/2025
1212

1313
You can contact the Microsoft Edge extensions support team to request help, submit feedback, or report a copyright or trademark infringement.
1414

15+
<!-- email is only used for [Transfer ownership of an extension](./update/transfer-ownership.md) -->
16+
1517

1618
<!-- ====================================================================== -->
1719
## Issues page in the MicrosoftEdge-Extensions repo

microsoft-edge/extensions/developer-guide/port-chrome-extension.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,17 +16,17 @@ To port your Chrome extension:
1616

1717
1. Review the Chrome extension APIs used in your extensions with the Microsoft Edge extensions [supported APIs](api-support.md) list.
1818

19-
If your extension uses APIs that aren't supported by Microsoft Edge, it might not port directly.
19+
If the extension uses APIs that aren't supported by Microsoft Edge, it might not port directly.
2020

2121
1. Remove the `update_url` field from the manifest file.
2222

23-
1. If `Chrome` is used in either the name or the description of your extension, rebrand your extension using `Microsoft Edge`. To pass the certification process, the changes are required.
23+
1. If `Chrome` is used in either the name or the description of your extension, rebrand the extension using `Microsoft Edge`. To pass the certification process, the changes are required.
2424

25-
1. Test your extension to check if it works in Microsoft Edge by [sideloading your extension](../getting-started/extension-sideloading.md).
25+
1. Test the extension to check if it works in Microsoft Edge by sideloading the extension. See [Sideload an extension to install and test it locally](../getting-started/extension-sideloading.md).
2626

27-
1. If you face any issues, you can debug your extensions in Microsoft Edge by using the DevTools, or [contact us](mailto:[email protected]).
28-
29-
1. Follow the [publishing guidelines](../publish/publish-extension.md) to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
27+
1. If you encounter any issues, you can:
28+
* Debug the extension in Microsoft Edge by using DevTools; see [Overview of DevTools](../../devtools/overview.md).
29+
* [Contact the Microsoft Edge extensions team](../contact.md).
3030

3131

3232
<!-- ====================================================================== -->
@@ -36,8 +36,10 @@ If your extension exchanges messages with a native app by using `chrome.runtime.
3636

3737

3838
<!-- ====================================================================== -->
39-
## Next steps
39+
## Publish the extension
4040

4141
After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com):
42-
1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md)
43-
1. [Publish a Microsoft Edge extension](../publish/publish-extension.md)
42+
43+
1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md).
44+
45+
1. [Publish a Microsoft Edge extension](../publish/publish-extension.md).
70.9 KB
Loading
51.9 KB
Loading
37.7 KB
Loading
486 Bytes
Loading
30.7 KB
Loading
25.9 KB
Loading
93.4 KB
Loading

0 commit comments

Comments
 (0)