Closed Bug 1790378 Opened 2 years ago Closed 2 years ago

Add timestamp to browsingContext navigation events

Categories

(Remote Protocol :: WebDriver BiDi, enhancement, P1)

Product:
Remote Protocol
Component:
WebDriver BiDi
Type:
enhancement
Points:
2

Tracking

(firefox110 fixed)

Status:
RESOLVED FIXED
Milestone:
110 Branch
Tracking Flags:
Tracking Status
firefox110 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

(
URL
)

Details

(Whiteboard: [webdriver:m5][wptsync upstream][webdriver:relnote])

Attachments

(2 files)

Bug 1790378 - [webdriver-bidi] Added timestamp to navigation info.
(deleted), text/x-phabricator-request
Details
Bug 1790378 - [wdspec] Enhance navigation tests for "timestamp" in navigation info.
(deleted), text/x-phabricator-request
Details

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

The WebDriver BiDi specification PR has been merged. As such we can get the timestamp added now.

Whiteboard: [webdriver:backlog:blocked] → [webdriver:backlog]
Assignee: nobody → hskupin
Status: NEW → ASSIGNED

Currently we only have browsingContext.domContentLoaded and browsingContext.load implemented.

No longer blocks: 1756594, 1775283
Priority: P2 → P1
Regressed by: 1756597, 1756617
Whiteboard: [webdriver:backlog] → [webdriver:m6]
No longer regressed by: 1756597, 1756617
Points: --- → 2
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8c175c957f35 [webdriver-bidi] Added timestamp to navigation info. r=webdriver-reviewers,jdescottes https://hg.mozilla.org/integration/autoland/rev/7c1c3dbacb6c [wdspec] Enhance navigation tests for "timestamp" in navigation info. r=webdriver-reviewers,jdescottes
Failed to create upstream wpt PR due to merge conflicts. This requires fixup from a wpt sync admin.
Whiteboard: [webdriver:m6] → [webdriver:m6], [wptsync upstream error]

(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!

Flags: needinfo?(james)
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/37834 for changes under testing/web-platform/tests
Whiteboard: [webdriver:m6], [wptsync upstream error] → [webdriver:m6], [wptsync upstream]
Flags: needinfo?(james)

https://hg.mozilla.org/mozilla-central/rev/8c175c957f35
https://hg.mozilla.org/mozilla-central/rev/7c1c3dbacb6c

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox110: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
Whiteboard: [webdriver:m6], [wptsync upstream] → [webdriver:m5], [wptsync upstream]
Upstream PR merged by moz-wptsync-bot
Whiteboard: [webdriver:m5], [wptsync upstream] → [webdriver:m6], [wptsync upstream]
Whiteboard: [webdriver:m6], [wptsync upstream] → [webdriver:m5], [wptsync upstream]
Blocks: 1810171
Whiteboard: [webdriver:m5], [wptsync upstream] → [webdriver:m5][wptsync upstream][webdriver:relnote]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: