-
Notifications
You must be signed in to change notification settings - Fork 172
Support for --remote-debugging-pipe #294
Copy link
Copy link
Open
Labels
kind:featureA request, idea or new functionalityA request, idea or new functionalitytopic:interfaceRelated to the interface exposed to the userRelated to the interface exposed to the usertopic:processRelated to the spawn, management and kill of the chromium processRelated to the spawn, management and kill of the chromium process
Description
Metadata
Metadata
Assignees
Labels
kind:featureA request, idea or new functionalityA request, idea or new functionalitytopic:interfaceRelated to the interface exposed to the userRelated to the interface exposed to the usertopic:processRelated to the spawn, management and kill of the chromium processRelated to the spawn, management and kill of the chromium process
I think adding support for
--remote-debugging-pipewould be beneficial, as it would not require the use of ports.It would also remove the need to discover which port it's listening on, which would remove the need to have the language set to English (according to the README).
I'm interested to work on this, I've experimented a bit here already: https://github.com/MidasLamb/chromium-debug-pipe/blob/main/src/main.rs to see how it works, and it seems pretty straightforward.