-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Edge support #161
Comments
Other relevant link from that issue: https://docs.microsoft.com/en-gb/microsoft-edge/extensions-chromium/#publishing-to-the-microsoft-edge-add-ons-website |
Another one to look into would be Brave https://brave.com/features/ Do they even have devtools? I'll work on the settings stuff some more tomorrow and will check out Edge (for Mac) and brave if I have time |
For brave support, I think we can point people to: https://support.brave.com/hc/en-us/articles/360017909112-How-can-I-add-extensions-to-Brave- And explain to them how to get the latest release artifact (from the tag) I might be having another look at publishing an Edge extension soon 🙂. |
Hello @HugoDF, If you have any more queries about porting Chrome extension to Microsoft Edge or anything else, you can contact the relevant teams whose links are given here - https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/contact-extensions-team. Let me know if this was helpful. I am happy to help you with more details. Thank you! |
Thanks @nagachaitanyalokam will do I think Edge is 1:1 with Chrome so should just be admin (sign up as a developer & fill out forms) |
+1 on this. Would love not to install Chrome just for this devtool. |
it's available on Firefox as well if that helps, I haven't been able to find much time to progress with this. |
FWIW you can install Chrome extensions on Edge, so this isn't such a big deal. |
Opening this issue after #154 became blocked due to missing
devtools
support.I think the process for getting Edge working will be easier than Safari because it's still Chromium under the hood. Haven't looked into it yet though.
The text was updated successfully, but these errors were encountered: