-
Notifications
You must be signed in to change notification settings - Fork 171
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 Diagnostic Adapter support #49
Comments
We provide a protocol.json for the Edge Diagnostics Adapter, so this documentation could easily be used to display the supported API of Edge. However, at Microsoft we want a common, independent protocol, that isn't maintained by one browser vendor, so if |
What is our plan for this issue. Do we still want to do this? |
Well I think this is now rendered incomplete by the Edge DevTools protocol (which is different from the diagnostics adapter, but is the Edge longterm plan) https://docs.microsoft.com/en-us/microsoft-edge/devtools-protocol/ |
Since we added support for multiple versions of the protocol, I've been thinking about including APIs supported by the Edge Diagnostic Adapter. @paulirish is on board with this idea. @auchenberg WDYT?
Only thing that we need to make this happen is a
protocol.json
file describing APIs supported by the Chrome Debugging Protocol endpoint in Edge.The text was updated successfully, but these errors were encountered: