Start Marionette in Fennec when remote debugging is enabled
Categories
(Firefox for Android Graveyard :: Testing, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: nalexander, Unassigned)
References
Details
In Bug 1524673, which I'm about to land, we make Marionette part of Remote Debugging. This mirrors Chrome/Chrome WebView and chromedriver: Remote Debugging (over CDP) is how you enable automation.
Fennec doesn't use GeckoView's setRemoteDebuggingEnabled
, so that ticket doesn't actually wire Marionette into Fennec. This ticket tracks that.
Historically we haven't enabled Marionette in Fennec, for reasons I don't fully understand: something about the security of the Marionette protocol never having been vetted in the way that the Remote Debugging Protocol has been vetted?
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
whimboo: can you connect this into the network of existing Fennec/Marionette tickets?
Reporter | ||
Comment 2•6 years ago
|
||
I am not intending to address this ticket unless there's a new and compelling reason to do so. I think our existing prefs-based system and test runners are probably sufficient.
Comment 3•6 years ago
|
||
Sorry, but I actually don't get what this ticket is about in detail. What is the goal of this bug?
Comment 4•6 years ago
|
||
(In reply to Nick Alexander :nalexander [he/him] from comment #0)
Historically we haven't enabled Marionette in Fennec, for reasons I don't fully understand: something about the security of the Marionette protocol never having been vetted in the way that the Remote Debugging Protocol has been vetted?
Updated•6 years ago
|
Comment 5•4 years ago
|
||
Updated•4 years ago
|
Description
•