1916685 - Fetch timings should be in milliseconds, not microseconds

Status: RESOLVED FIXED

(Remote Protocol :: WebDriver BiDi, defect, P2)

Description

[Julian Descottes [:jdescottes]]

Per spec, the network event timestamps should be in milliseconds, however we return a value in microseconds at the moment.

https://www.w3.org/TR/hr-time-3/#dom-domhighrestimestamp

All timings from platform are in microseconds, and we didn't think about converting them.

Comment 2

[Julian Descottes [:jdescottes]]

Attachment: Bug 1916685 - [bidi] Convert all network event timings to milliseconds

Platform timestamps are in microseconds, while we expect network event timings in milliseconds

Comment 3

[Julian Descottes [:jdescottes]]

Attachment: Bug 1916685 - [wdspec] Update several network bidi tests to assert timings

Depends on D221033

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d9a88df573cb
[bidi] Convert all network event timings to milliseconds r=webdriver-reviewers,whimboo
https://hg.mozilla.org/integration/autoland/rev/e1aade50c0eb
[wdspec] Update several network bidi tests to assert timings r=webdriver-reviewers,whimboo

Comment 5

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/d9a88df573cb
https://hg.mozilla.org/mozilla-central/rev/e1aade50c0eb

Comment 6

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/48277 for changes under testing/web-platform/tests

Comment 7

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot

Comment 8

[Julian Descottes [:jdescottes]]

The BiDi har exporter was updated to handle both timings in milliseconds or microseconds in https://github.com/firefox-devtools/bidi-har-export/releases/tag/v0.0.15