Closed yume-chan closed 1 year ago
Microsoft Edge actually serves their DevTools files at https://devtools.azureedge.net/serve_file/@0a8f453929e6410c973aa529a40485ce4e3e03db/inspector.html
It might not be usable due to licensing issue.
hey, off-topic question, but how do I make https://devtools.azureedge.net/serve_file/@0a8f453929e6410c973aa529a40485ce4e3e03db/inspector.html load a webpage, or is it just a visual thing?
It doesn't load pages directly. In remote debugging scenarios, it uses WebSocket to connect to a remote debugging port.
oh, ok
hey, would it be possible to extend this functionality to other browsers, such as opera, edge, and/or firefox?
hey, I noticed that it only works for opera, but it doesn't work for opera beta, opera gx, mini, or others. also, I just tried to use it with edge, but the popup gets stuck on a white screen, but it works normally on edge beta.
Opera beta added. Opera GX uses WebView and doesn't enable remote debugging. mini not tested.
Opera (both stable and beta) is still using Chromium 75 so really not recommended.
Edge doesn't host its DevTools for stable versions (beta, dev and canary all hosted, although hidden). So I decide to use Chrome's hosted version for all browsers (including Opera) instead.
oh, ok. thanks
I tested Opera mini stable, beta, opera touch, and Opera crypto browser, but Tango doesn't connect to any of them.
Opera mini, Opera mini beta, Opera touch and Opera crypto browser also don't have their remote debugging enabled.
Chrome remote debugger is another not that useful, but also not that hard to implement feature for demonstrating using ADB.
Basic flow:
/json
HTTP request tolocalabstract:chrome_devtools_remote
Implementation details:
ws
or other WebSocket package for Node.jspostMessage
messagesiframe
with a new route in Next.jsglobalThis.InspectorFrontendHost
that communicates with the "Embedder" (https://github.com/ChromeDevTools/devtools-frontend/blob/d8339c3c10307b8a5635214d9fec607c14c189fd/front_end/core/host/InspectorFrontendHost.ts#L458-L484)<script>
to loadinspect.js
from specified Chrome DevTools Frontend versionOpen questions:
devtoolsFrontendUrl
field in/json
response. Test how Chrome reacts to it.