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