Port the usage of the RDP protocol over to WebDriver BiDi

[whimboo]

With WebDriver BiDi being adopted by more and more test and automation frameworks due to its cross-browser compatibility it would be great to see the web-ext tool also making use of WebDriver BiDi. Firefox' own RDP protocol via DevTools is not standardized and may surface changes which require clients to update their code. WebDriver BiDi APIs are stable and backward compatible.

It would be good to know which specific APIs for RDP are used by web-ext that are required to be supported by WebDriver BiDi. We may not support all of these yet, so having a list would certainly help us to prioritize / schedule remaining work to unblock a change of the underlying protocol.

CC @zombie, @rpl and @Rob--W

[rpl]

@whimboo here is a list of the Firefox RDP methods web-ext is using:

• addons RDP actor listAddons: (

  web-ext/src/firefox/remote.js

  Line 130 in c8bb142

  const response = await this.client.request('listAddons');

  )
• addons RDP actor installTemporaryAddon (

  web-ext/src/firefox/remote.js

  Line 115 in c8bb142

  type: 'installTemporaryAddon',

  )
• addon RDP actor reload (

  web-ext/src/firefox/remote.js

  Line 174 in c8bb142

  await this.addonRequest(addon, 'reload');

  )

[Rob--W]

Install and re-install are currently the only supported operations in webdriver-bidi, added in w3c/webdriver-bidi#778 and rendered at https://w3c.github.io/webdriver-bidi/#module-webExtension

The ability to retrieve the list of extensions and to reload individual extensions (at least to refresh the updated extension sources, without losing web/extension data) are not part of the protocol yet.

[Rob--W]

@rpl provided the following additional context:

Bidi meta bugs being worked on at the moment:

• Bug 1934549 - [meta] Support "webExtension.install" command
• Bug 1934552 - [meta] Support "webExtension.uninstall" command

and a comment from Henrik related to reloading the extension

• Only reloading might be a problem right now given that we do not yet allow evaluation of scripts in the parent process. But I'm going to start working on it soon via https://bugzilla.mozilla.org/show_bug.cgi?id=1944570
• Bug 1944570 - Support executing “script.evaluate” and “script.callFunction” for browsing contexts in the parent process

(/end of @rpl comment)

About reloading - I'll discuss with other browser vendors about the appetite for supporting extension reloading as a first class feature. I can imagine a potential implementation to re-use the webExtension.install method.

[whimboo]

@rpl provided the following additional context:
and a comment from Henrik related to reloading the extension

* Only reloading might be a problem right now given that we do not yet allow evaluation of scripts in the parent process. But I'm going to start working on it soon via https://bugzilla.mozilla.org/show_bug.cgi?id=1944570

* [Bug 1944570 - Support executing “script.evaluate” and “script.callFunction” for browsing contexts in the parent process](https://bugzilla.mozilla.org/show_bug.cgi?id=1944570)

Actually those two bugs wont be needed when we are ok with having the webExtension.listAddons and webExtension.reloadAddon() (or similar naming) as part of the specification. I think it makes sense to add them. I'll do when I'm back from vacation so that we can discuss it in the next month W3C meeting.

Thanks for all the helpful information!