Closed
Bug 1916427
Opened 1 year ago
Closed 1 year ago
[wdspec] Add test for order of "browsingContext.navigationStarted" and "network.beforeRequestSent" events
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Remote Protocol
WebDriver BiDi
Tracking
(firefox132 fixed)
RESOLVED
FIXED
132 Branch
| Tracking | Status | |
|---|---|---|
| firefox132 | --- | fixed |
People
(Reporter: Sasha, Assigned: Sasha)
Details
(Whiteboard: [webdriver:m12], [wptsync upstream])
Attachments
(1 file)
We have a couple of puppeteer tests which rely on the right order of "browsingContext.navigationStarted" and "network.beforeRequestSent" events (the navigation event should come first), e.g., this, but at the moment we don't have an exact wdspec test. This test is quite close but since it utilizes history API we fail it now, because we don't send browsingContext.fragmentNavigated. So we should add a similar test but with a simple page.
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → aborovova
Status: NEW → ASSIGNED
Pushed by aborovova@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8d1a7a57dd38
[wdspec] Add test for order of "browsingContext.navigationStarted" and "network.beforeRequestSent" events. r=webdriver-reviewers,jdescottes
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/47981 for changes under testing/web-platform/tests
| Assignee | ||
Updated•1 year ago
|
Points: --- → 2
Priority: -- → P2
Whiteboard: [webdriver:m12]
Comment 4•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox132:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
Upstream PR merged by moz-wptsync-bot
Whiteboard: [webdriver:m12] → [webdriver:m12], [wptsync upstream]
You need to log in
before you can comment on or make changes to this bug.
Description
•