Possibility to register devices/pages under chrome://inspect

[Kenneth Auchenberg]

Hi everyone,

I'm these days exploring ways to unify remote debugging between Firefox and Chrome, by writing a firefox-to-chrome-bridge that simply provides a Chrome remote debug protocol interface for Firefox. This enables Chrome DevTools (and other integrations) to remote Firefox in a transparent way, and is a part of a bigger vision to provide a unified remote debugging interface for all browsers.

It's still early days, but I got the basic DOM operations working, and is currently exposing a HTTP interface on /json, to provide the same interface as a Chrome-endpoint. My idea with this HTTP-endpoint is to make Firefox-endpoints discoverable by Chrome. I want to make the Firefox tabs/apps appear in chrome://inspect. The layout of chrome://inspect seem to be somewhat prepared for this with the "other" tab.

But when looking into the internals of chrome://inspect, the device-data seems to come from a internal-VM-call within Chrome, that invokes the populateLists-method in inspect.js. This means I can't intercept the request/call, which was my original idea.

Is there any way I can intercept or register devices for chrome://inspect?

Thanks.

/k