Add timestamp to browsingContext navigation events
Categories
(Remote Protocol :: WebDriver BiDi, enhancement, P1)
Tracking
(firefox110 fixed)
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
()
Details
(Whiteboard: [webdriver:m5][wptsync upstream][webdriver:relnote])
Attachments
(2 files)
As of now all the browsingContext related navigation events do not have a timestamp set. To measure performance based on these events a timestamp should be added.
There is the following GitHub issue open to get this entry added:
https://github.com/w3c/webdriver-bidi/issues/271
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
The WebDriver BiDi specification PR has been merged. As such we can get the timestamp added now.
| Assignee | ||
Comment 2•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Comment 3•3 years ago
|
||
Depends on D166381
| Assignee | ||
Comment 4•3 years ago
|
||
Currently we only have browsingContext.domContentLoaded and browsingContext.load implemented.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 7•3 years ago
|
||
(In reply to Web Platform Test Sync Bot (Matrix: #interop:mozilla.org) from comment #6)
Failed to create upstream wpt PR due to merge conflicts. This requires fixup
from a wpt sync admin.
Hi James, could you please check why the upstream PR could not be created? Thanks!
Updated•3 years ago
|
Comment 9•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8c175c957f35
https://hg.mozilla.org/mozilla-central/rev/7c1c3dbacb6c
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
Description
•