Remove the "remote.enabled" preference
Categories
(Remote Protocol :: Agent, task, P2)
Tracking
(firefox90 fixed)
Tracking | Status | |
---|---|---|
firefox90 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [bidi-m1-mvp])
Attachments
(1 file)
Currently the availability of the Remote Agent is being controlled via the remote.enabled
preference. And only with this preference set to true
the command line argument --remote-debugging-port
will be available, which initializes the Remote Agent and makes it available within Gecko.
Given that we are basically out of the experimental phase for CDP and no longer restrict the Remote Agent to Firefox Nightly only, there seems to be no reason to actually keep this preference around.
Seeing the pref gone will also help me with combining the build flags for Marionette and Remote Agent over on bug 1695031. Then both Marionette and Remote Agent will show the same behavior and can be started via the command line arguments.
Assignee | ||
Comment 1•4 years ago
|
||
Instances of this preference can be found here:
https://searchfox.org/mozilla-central/search?q=remote.enabled&path
Assignee | ||
Comment 2•3 years ago
|
||
Freddy, mind having a look at comment 0? Do you see any kind of security implication when we are going to remove the preference and make the Remote Agent always available via the command line argument. This would be inline with Marionette, and we soon will require it for the WebDriver BiDi implementation. Thanks.
Comment 3•3 years ago
|
||
Given that you already (and will continue to) require a command line parameter to be present for it to be enabled, I don't see any obvious risks.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
Comment 6•3 years ago
|
||
bugherder |
Description
•