Add support for vendor specific WebDriver BiDi modules
Categories
(Remote Protocol :: WebDriver BiDi, enhancement, P3)
Tracking
(firefox138 fixed)
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: whimboo, Assigned: jdescottes)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [webdriver:m15])
Attachments
(1 file, 2 obsolete files)
For Mozilla specific APIs in our WebDriver BiDi implementation we need a way to handle vendor specific commands and events. In our case commands could look like moz:debugger.start
.
To properly separate such modules from those that are officially part in the WebDriver Bidi specification, we should put those into their own folder. We should potentially call it moz
.
As such our code in the WebDriverBiDiConnection module should not only split by .
, but also :
to check for potential prefixes, and handle them if appropriate. Routing should basically be similar to the other modules.
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Assignee | ||
Comment 4•7 months ago
|
||
Nazim, do you mind if I take over this one?
I can provide a patch with tests for the framework part.
Yes, please feel free to take over this one.
Assignee | ||
Comment 6•7 months ago
|
||
This adds tests and framework support for vendored modules in MessageHandler
We also add the moz: prefix to the WebDriver BiDi ModuleRegistry
Assignee | ||
Comment 7•7 months ago
|
||
Depends on D241233
(not intended for review, just an example)
Assignee | ||
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Assignee | ||
Updated•7 months ago
|
Comment 9•7 months ago
|
||
bugherder |
Description
•