Closed
Bug 1836926
Opened 2 years ago
Closed 2 years ago
Rename originTime to timeOrigin in network events fetchTimingInfo
Categories
(Remote Protocol :: WebDriver BiDi, defect, P1)
Remote Protocol
WebDriver BiDi
Tracking
(firefox116 fixed)
RESOLVED
FIXED
116 Branch
Tracking | Status | |
---|---|---|
firefox116 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [webdriver:m7], [wptsync upstream][webdriver:relnote])
Attachments
(2 files)
We misnamed the property timeOrigin
as originTime
and we also missed to verify this in our tests.
Assignee | ||
Comment 1•2 years ago
|
||
We misnamed this field in the initial implementation, so this makes it consistent with the spec at
https://w3c.github.io/webdriver-bidi/#type-network-FetchTimingInfo
Updated•2 years ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D180064
Updated•2 years ago
|
Severity: -- → S3
Points: --- → 1
Priority: -- → P1
Whiteboard: [webdriver:m7]
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bd0ff6dae074
[bidi] Rename originTime to timeOrigin in network events fetchTimingInfo r=webdriver-reviewers,whimboo
https://hg.mozilla.org/integration/autoland/rev/832a5840ccf7
[wdspec] Check timeOrigin in BiDi fetch timing info tests r=webdriver-reviewers,whimboo
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/40396 for changes under testing/web-platform/tests
Whiteboard: [webdriver:m7] → [webdriver:m7], [wptsync upstream]
Comment 5•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/bd0ff6dae074
https://hg.mozilla.org/mozilla-central/rev/832a5840ccf7
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox116:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
Upstream PR merged by moz-wptsync-bot
Assignee | ||
Updated•2 years ago
|
Whiteboard: [webdriver:m7], [wptsync upstream] → [webdriver:m7], [wptsync upstream][webdriver:relnote]
You need to log in
before you can comment on or make changes to this bug.
Description
•