Unwanted "Browser under remote control"
Categories
(Remote Protocol :: Agent, defect)
Tracking
(Not tracked)
People
(Reporter: amanteaux, Unassigned)
References
Details
Attachments
(1 file)
|
33.75 KB,
image/png
|
Details |
firefox_remote_control.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
Sometimes after a new Firefox Developer update, when I use the browser normally as a human (I have never used selenium or any automated browser scenario on this desktop), Firefox is running in the "Browser is running under remote control" mode.
That is really a pain because the URL are completely non readable, and I am not sure about security implications.
Actual results:
Running Firefox in recovery mode removes this "Browser is running under remote control" mode. However, disabling all the extensions/themes/plugins doesn't change anything.
It happened a first about 2 weeks ago and it solved itself magically after 1-2 days.
But it is now happening again today
Expected results:
I want to completely remove "Browser is running under remote control" mode. I don't want this mode to be enabled magically by any reason. This must be enabled only either by a preference in the "about:config" menu, or either by a program argument parameter specified during the browser start up.
|
||
Comment 1•4 years ago
|
||
Hi, I'm not sure if this is the correct component for this issue but it seems that Remote control is activated randomly after an update, maybe one of our developers can take a look and they might know what could be the cause of it, what is triggering this feature.
Also I think the UX for it might be fixed with Bug 1594435.
|
||
Comment 2•4 years ago
|
||
Thanks for filing the bug amanteaux. Would you mind telling me if you are actually making use of the Firefox DevTools and specifically the Browser Toolbox? That could be the only offender here given that you aren't using any automation tools that utilize WebDriver (geckodriver/Marionette) nor CDP (Remote Agent).
Hi Henrik,
Thank you for this answer.
So actually I have just realized that I use a special Firefox program argument: --start-debugger-server 6000
I have never really used it... but it was there... Removing it solves my issue.
Sorry for the inconvenience, I should have verified the command line argument sooner.
|
|
||
Comment 4•4 years ago
|
||
Good to know. Thank for letting us know.
Description
•