- Sep 10, 2015
- 147
- 140
- 158
Basics: Using DevTools as protocol client
The Developer Tools front-end can attach to a remotely running Chrome instance for debugging. For this scenario to work, you should start your host Chrome instance with the remote-debugging-port command line switch:
The Developer Tools front-end can attach to a remotely running Chrome instance for debugging. For this scenario to work, you should start your host Chrome instance with the remote-debugging-port command line switch:
Code:
"C:\Program Files\TeamSpeak\TeamSpeak.exe" --remote-debugging-port=9222{
"Browser": "Chrome/78.0.3904.63",
"Protocol-Version": "1.3",
"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.63 Safari/537.36",
"V8-Version": "7.8.279.17",
"WebKit-Version": "537.36 (@227acb8a7550cb84014465e16f422bccb5462def)",
"webSocketDebuggerUrl": "ws://localhost:9222/devtools/browser/****"
}
"Browser": "Chrome/78.0.3904.63",
"Protocol-Version": "1.3",
"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.63 Safari/537.36",
"V8-Version": "7.8.279.17",
"WebKit-Version": "537.36 (@227acb8a7550cb84014465e16f422bccb5462def)",
"webSocketDebuggerUrl": "ws://localhost:9222/devtools/browser/****"
}
Last edited:
