-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to go to the new edge browser extension store #1
Comments
I found the edge add-on store has this extension already, see https://microsoftedge.microsoft.com/addons/detail/crx-extractordownloader/gfgehnhkaggeillajnpegcanbdjcbeja. The chrome version is on https://chrome.google.com/webstore/detail/ajkhmmldknmfjnmeedkbkkojgobmljda. I can't tell is it an official one. But I tested both of them, they were not working as expected, both of them could not download crx/zip from the edge add-on store. |
确实有可能是别人盗的。Edge商店也没有Chrome商店那么开放。 |
@ChirmyRam The extension is released by me but under different name. I just love the tonystark name so i just used it to create the username with that name. @liudonghua123 |
Well, thank you very much. But at the moment I'm not responding to download extensions with it, and I'm looking forward to updates. |
For now, power users can manually download CRX files from Edge Addons store by substituting Example, for https://microsoftedge.microsoft.com/addons/detail/pride-%E2%80%93-bisexual/jjamdofabacbjoobjmfppbamldncchmm, |
@win98se @liudonghua123 @ChirmyRam In the Latest MR the changes are available. Will publish the changes in a day or two |
The new version of edge browser based on chrome kernel has been released. The extension can be put on the edge store free of charge. It is compatible with Chrome extension, and the number of users is increasing gradually.
So I hope that this extension can be put on the edge store to make it easier for more people to access this extension.And I hope it can extract the extensions of edge extension store in the same way.
Thank you very much.
The text was updated successfully, but these errors were encountered: