Skip to content
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

Closed
kdzwinel opened this issue May 13, 2016 · 4 comments
Closed

Edge Diagnostic Adapter support #49

kdzwinel opened this issue May 13, 2016 · 4 comments

Comments

@kdzwinel
Copy link
Contributor

kdzwinel commented May 13, 2016

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.

@auchenberg
Copy link
Contributor

auchenberg commented May 15, 2016

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 debugger-protocol-viewer would gain Edge support, I'd like to see it live on a non-browser place like RemoteDebug or somewhere entirely new.

@paulirish
Copy link
Member

@TimvdLippe
Copy link
Contributor

What is our plan for this issue. Do we still want to do this?

@paulirish
Copy link
Member

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/
https://docs.microsoft.com/en-us/microsoft-edge/devtools-protocol/0.1/domains/
https://www.youtube.com/watch?v=VhJA2yKp_y8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants