Finalize ModuleRegistry implementation
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Tracking
(firefox95 fixed)
Tracking | Status | |
---|---|---|
firefox95 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [bidi-m2-mvp] )
Attachments
(2 files, 1 obsolete file)
We introduced a simple ModuleRegistry in https://bugzilla.mozilla.org/show_bug.cgi?id=1694144 in order to reference all existing modules and avoid test failures from browser/base/content/test/static/browser_all_files_referenced.js
But in the long run, we would like ModuleRegistry to have more responsibilities:
- check if a given module has an implementation for a given context+destination
- check list of commands supported by a module
- check list of events supported by a module
The goal of this bug is to improve the current ModuleRegistry to match the description above. This should make error reporting easier, so this blocks Bug 1724411.
It will probably also make Bug 1723592 redundant.
Assignee | ||
Comment 1•3 years ago
|
||
The ModuleRegistry can now be used to import BiDi modules.
The ModuleCache can be queried to get all the relevant modules for a moduleName+destination pair.
Error messages have been improved and are verified with a dedicated test
Assignee | ||
Comment 2•3 years ago
|
||
Depends on D123655
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
Depends on D123655
Add a dedicated Errors module to remote/shared/messagehandler, similar to shared/webdriver/Errors.jsm
Errors thrown from content process MessageHandler are serialized before being forwarded to the parent process.
We should probably make all errors inherit from a generic RemoteError class which would support the same serialization/deserialization API
Updated•3 years ago
|
Comment 6•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4490d6e92109
https://hg.mozilla.org/mozilla-central/rev/a3ac7e932f3a
Description
•