Hi, I manage an extension that adds several panels to classic devTools to inspect a remote target. Since the version 83 of Chrome, these additional panels don't load in certain conditions.
Our usual process is to open chrome://inspect/#devices then select the remote target to inspect, or click on "Open dedicated DevTools for Node". That opens a devTools with extension and so additional inspect/debug features.
With chrome 83, we have to inspect the remote target to have the logs, then open devTools in any http page if we want to access our additional features but these are not loaded anymore in the devTools opened to inspect remote Node.
I've managed to create a minimalist extension where i reproduce the exact same issue, see
https://github.com/Erwan-Laurent-Wiztivi/devToolsExtensionMin. That makes me think this issue is on Google Chrome side instead of our extension. It seems to be related to the protocol used : http or any equivalent webpage seems OK, but file:// protocol used when inspecting our remote target doesn't work anymore. I also tried several chrome:// page, they don't work anymore while chrome-search:// or chrome-extension:// are working (by working I mean additional panels are present when opening devTools).
Is it a security improvement I missed and can it be fixed on my side ? Is it a (known) issue on Google Chrome side ? If there is any missing info or a similar topic already opened (didn't find) please let me know.
See the issue in images : one for v81, one for v83, with on top the remote target and its devTools, on bottom chrome default page and its devTools. Notice the absence of >> for remote target to display other panels in v83 image