Combine ENABLE_MARIONETTE and ENABLE_REMOTE_AGENT build options for BiDi
Categories
(Remote Protocol :: Agent, task, P2)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
Details
It should be considered to combine both build options to be able to control Marionette and WebDriver BiDi with the same option. Maybe we can use ENABLE_WEBDRIVER for it.
Note that this also blocks us right now to move e.g the Marionette code over to /remote, because it wouldn't be build if ENABLE_REMOTE_AGENT is disabled.
|
Reporter | |
Updated•4 years ago
|
|
|
Reporter | |
Comment 1•4 years ago
|
||
Hi Geoff, with our ongoing efforts to implement WebDriver BiDi we want to merge Marionette into Remote Agent, which is the component that will contain the WebDriver Bidi implementation. Therefore we want to merge both build flags. And as a follow-up all JS files from /testing/marionette will be moved to /remote/marionette.
Also Remote Agent (which currently implements parts of the Chrome-DevTools protocol) is currently not enabled in Thunderbird, and would then be implicitly required.
Would you mind giving me a quick update in how Thunderbird currently utilizes Marionette? And would the above changes cause problems? Maybe enabling the Remote Agent should be done first?
I'm also happy to chat via Zoom or equivalent if wanted, which might help to get you a better idea of the upcoming project. Thanks!
|
||
Comment 2•4 years ago
|
||
We're using Marionette for a single lonely test (that's going to be obsolete soon anyway) and for starting Mochitest. I think if we enable Remote Agent the changes here shouldn't cause us any problems. I'll start a new bug for that.
|
|
Reporter | |
Comment 3•4 years ago
|
||
This is actually already covered by bug 1695031.
Description
•