Closed
Bug 1810171
Opened 2 years ago
Closed 2 years ago
[wdspec] Add missing timestamp assertion in assert_navigation_info
Categories
(Remote Protocol :: WebDriver BiDi, enhancement, P1)
Remote Protocol
WebDriver BiDi
Tracking
(firefox110 fixed)
RESOLVED
FIXED
110 Branch
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [webdriver:m5])
Attachments
(1 file, 1 obsolete file)
On bug 1790378 I've added the new timestamp
property to the navigation events. As noticed by Maksim on the upstream PR we miss the actual assertion for the timestamp.
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Attachment #9312200 -
Attachment is obsolete: true
Assignee | ||
Updated•2 years ago
|
Points: --- → 1
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d6813678e069
[wdspec] Add missing assertion for navigation event's timestamp. r=webdriver-reviewers,jdescottes
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/37944 for changes under testing/web-platform/tests
Comment 5•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
Comment 6•2 years ago
|
||
Is this the correct format for the assertion? At the top of the function, it's indicated timestamp
is expected to be an integer.
Flags: needinfo?(hskupin)
Updated•2 years ago
|
Whiteboard: [webdriver:m5]
Assignee | ||
Comment 7•2 years ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #6)
Is this the correct format for the assertion? At the top of the function, it's indicated
timestamp
is expected to be an integer.
Yes, integer is the default but for specific timestamp related checks we actually pass in a time interval given that we cannot check for exact timestamps.
Flags: needinfo?(hskupin)
Upstream PR merged by jgraham
You need to log in
before you can comment on or make changes to this bug.
Description
•