Publish extension to Microsoft Edge Add-ons

[MPThLee]

MS Edge is based on Chromium now since 2020 according to Wikipedia, It is compatible with Chrome version without changing core codes. (Some of extension API that related to Google is removed on Edge but doesn't used on here.)

As The browser comes with External store compatiblity especially Chrome Webstore), It's easy to install and use. However, As it is Extetrnal, User need to allow the setting to continue. (See below image)

So, Why not to publish the extension on Microsoft Edge Add-ons? It's just CWS but for Edge.

Porting is simple. As both runs on same engine, Just rebrand on name and descriotion (eg: Chrome to Edge) and remove update_url (which is required for other side too.).

Any other steps are Create edge developer account on Partner center and Publish extension to their store. (Both are MS documentation)

But, As of July 2022, Microsoft is not accepting new Manifest v2` extensions as of migrating to Manifest V3.
So should refactor code with v3 compatible. It is same for other browser. (Releated: #4075)

This issue is higly related with #2076

[philc]

Thanks for filing this and for the various pointers. I'll take a look! As you say, Vimium needs to be migrated to manifest v3 before publishing, and I'm not yet sure how big of a change that will be, but it's planned for early this year.

…

On Thu, Jan 19, 2023 at 7:17 PM, MPThLee < ***@***.*** > wrote: MS Edge is based on Chromium now since 2020 according to Wikipedia ( https://en.wikipedia.org/wiki/Microsoft_Edge#New_Edge_(2019%E2%80%93present) ) , It is compatible with Chrome version without changing core codes. (Some of extension API that related to Google is removed on Edge but doesn't used on here.) As The browser comes with External store compatiblity especially Chrome Webstore), It's easy to install and use. However, As it is Extetrnal , User need to allow the setting to continue. (See below image) image ( https://user-images.githubusercontent.com/26970092/213607520-7fdca1f3-eeda-482f-9070-5dea78084312.png ) So, Why not to publish the extension on Microsoft Edge Add-ons ( https://microsoftedge.microsoft.com/addons/Microsoft-Edge-Extensions-Home ) ? It's just CWS but for Edge. Porting is simple ( https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension ). As both runs on same engine, Just rebrand on name and descriotion (eg: Chrome to Edge ) and remove update_url (which is required for other side too.). Any other steps are Create edge developer account on Partner center ( https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/create-dev-account ) and Publish extension to their store ( https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/publish-extension ). (Both are MS documentation) *But* , As of July 2022, Microsoft is not accepting new Manifest v2` extensions as of migrating to Manifest V3 ( https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/manifest-v3 ). So should refactor code with v3 compatible. It is same for other browser. (Releated: #4075 ( #4075 ) ) This issue is higly related with #2076 ( #2076 ) — Reply to this email directly, view it on GitHub ( #4211 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAACDFVMCOYUPQOHMFEAVHDWTH7TTANCNFSM6AAAAAAUBB6N3I ). You are receiving this because you are subscribed to this thread. Message ID: <philc/vimium/issues/4211 @ github. com>

[philc]

Hey @MPThLee, Vimium is now on the Edge Add-ons site. Please leave a review there to help encourage others to try it.

Thanks!