Add Chrome direct debug support (without requiring to install ADB)

[gunta]

I submitted a ticket here 1 year ago, but current status is WontFix because "We are experimenting with alternative ways of implementing wireless debugging".

As long as there is any update on this, we need to update this ticket.

[paulirish]

Not sure if this is related yet.... (and will fork to separate issue if neccessary).

I'd love to see a better integration with Remote Debugging.

The ideal might be something like this:

• For the attached device, you have a listing of the open tabs under the input field to launch a new one.
• You have an inspect button for them, clicking them opens devtools, probably embedded into STF instead of a separate window. So I still get the minicap + interaction of stf but with the full devtools over debugger protocol

about:inspect isn't very hackable however @auchenberg knows of some work that can access the same data.
(edit: ah he's using adbkit in adb-devtools-devices :)

And I think it may be possible to them do a iframe pointing to chrome-devtools://devtools/bundled/inspector.html?ws=localhost:2015

[gunta]

@paulirish
That sounds good.

For the attached device, you have a listing of the open tabs under the input field to launch a new one.

I'm a bit unsure about this one, listing all the tabs open in a device might make it browser-dependent (unless we can make tab listing work even on default browsers).

You have an inspect button for them, clicking them opens devtools, probably embedded into STF instead of a separate window. So I still get the minicap + interaction of stf but with the full devtools over debugger protocol

Does this kind of interaction would be possible without requiring the security permissions of a Chrome extension?

[paulirish]

might make it browser-dependent

Aye, I think it'd work where there's support. I'm not totally clear on the remote debugging story for Chromium forks, but one would imagine it'd be similar. :)

Does this kind of interaction would be possible without requiring the security permissions of a Chrome extension?

It doesn't sound impossible to me yet, but let me confirm these ideas with some engineers on my team first. :) We'll find out how far my ideal is from reality.

[auchenberg]

Pitching in here: I've written a little node module that findes devtools targets on a given device via ADB, and setups for the port forwarding, and lists the available remote debuggable tabs. It's early days, but you can see the flow here https://github.com/auchenberg/adb-devtools-devices

It's basically what chrome://inspectdoes for Android devices.