Implement basic support for log.entryAdded
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Tracking
(firefox94 fixed)
| Tracking | Status | |
|---|---|---|
| firefox94 | --- | fixed |
People
(Reporter: whimboo, Assigned: jdescottes)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [bidi-m1-mvp], [wptsync upstream])
Attachments
(4 files)
|
Assignee | |
Updated•4 years ago
|
|
Reporter | |
Comment 1•3 years ago
|
||
For the demo at the end of M1 we only need the basic support for this events means handling of just string messages. Anything else will be done at a later point and tracked via the meta bug 1719287.
|
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
|
Assignee | |
Comment 3•3 years ago
|
||
Depends on D122109
|
|
Assignee | |
Comment 4•3 years ago
|
||
Depends on D122109
|
||
Comment 5•3 years ago
|
||
When using the BiDiSession class we need the event loop to live at
least as long as a specific connection, but not necessarily as long as
the BiDISession object itself. Therefore we move the loop parameter
into the start() method, to associate a loop with a specific connection.
In addition, in the tests we make the event loop a global so that it
lives as long as a session; the fixture is updated to reuse the
existing loop where possible. This has the tradeoff that we're more
likely to share a loop between tests, so there is some additional
hidden shared state.
|
||
Updated•3 years ago
|
|
||
Comment 8•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/002f6e22802f
https://hg.mozilla.org/mozilla-central/rev/798401a59fee
https://hg.mozilla.org/mozilla-central/rev/908c3e478858
https://hg.mozilla.org/mozilla-central/rev/9e1434237651
Description
•