Removal of reference to platform-issues within "README.md". #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
July 31, 2022 14:56
I believe that "https://blogs.windows.com/msedgedev/2016/04/06/edgehtml-issue-tracker/" was for EdgeHTML, rather than Microsoft's fork of Chromium, which is the new Edge.
|
Did you test that it works on Chromium-based Edge? (Also, why remove the double-space? The README otherwise consistently uses them, I believe.) |
|
@dbaron, Microsoft Edge currently supports all of the WebExtension features that Chromium does. It is merely a derivative of Chromium whose interface is different. However, if you are able to inform me of what to do to evaluate whether Edge supports the extension, I've Edge installed for that purpose. I did not notice any additional double-spaces. Thanks for the notification. I have removed the additional double-space. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I believe that "https://blogs.windows.com/msedgedev/2016/04/06/edgehtml-issue-tracker/" was for EdgeHTML, rather than Microsoft's fork of Chromium, which is the new Edge.