Implement "browsingContext.historyUpdated" event
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Tracking
(firefox141 fixed)
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: whimboo, Assigned: jdescottes)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [webdriver:m16][wptsync upstream][webdriver:relnote])
Attachments
(6 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
Bug 1906051 - [wdspec] Update wdspec tests for fragment navigated to check event counts with iframes
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
This bug is used to implement the browsingContext.historyUpdated event. We can start the work once https://github.com/w3c/webdriver-bidi/pull/740 got merged.
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Updated•11 months ago
|
| Assignee | ||
Updated•9 months ago
|
| Assignee | ||
Comment 3•9 months ago
|
||
| Assignee | ||
Comment 4•9 months ago
|
||
| Assignee | ||
Comment 5•9 months ago
|
||
Backed out for causing puppeteer failures @ navigation.spec.js
| Assignee | ||
Comment 10•9 months ago
|
||
I missed the puppeteer failures on my try push, sorry about that.
For the first issue, we seem to run into the same issue as for Puppeteer with Chrome https://searchfox.org/mozilla-central/rev/b5ab48b8c33faf53817cb2ef64c8523a469ef695/remote/test/puppeteer/test/TestExpectations.json#1311-1317
{
"testIdPattern": "[navigation.spec] navigation Page.goto should work when reload causes history API in beforeunload",
"platforms": ["darwin", "linux", "win32"],
"parameters": ["chrome", "webDriverBiDi"],
"expectations": ["FAIL"],
"comment": "https://github.com/GoogleChromeLabs/chromium-bidi/issues/2856 historyUpdated from beforeunload incorrectly comes before navigationStarted."
},
We get historyUpdated before navigationStarted, which mostly relates to Bug 1908952 (see my last comment there).
For the second issue, we fail to emit historyUpdated events when using history.back() / forward() if the history navigation only updates the state.
Basically if I do
history.pushState({}, "", "1");
history.pushState({}, "", "2");
history.back();
I should get 3 historyUpdated events, but the location change for history.back() does not pass the test progress.loadType & Ci.nsIDocShell.LOAD_CMD_PUSHSTATE. Instead of LOAD_CMD_PUSHSTATE, we have LOAD_CMD_HISTORY.
But a location change with LOAD_CMD_HISTORY could also mean using back() to perform a regular same document navigation (eg #hash2 -> #hash1). The only difference seems to be with the flags passed to the locationChange callback. When back() only performs a history traversal, flags==1 and when it performs a hash change, flags==9. But I couldn't find any documentation for those load flag values.
| Assignee | ||
Comment 12•9 months ago
|
||
| Assignee | ||
Comment 13•9 months ago
|
||
| Assignee | ||
Comment 14•9 months ago
|
||
| Assignee | ||
Updated•9 months ago
|
Comment 15•9 months ago
|
||
Comment 17•9 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/a05801736679
https://hg.mozilla.org/mozilla-central/rev/c5176cef9407
https://hg.mozilla.org/mozilla-central/rev/cecc4bb3d0a6
https://hg.mozilla.org/mozilla-central/rev/0af66ba7393c
https://hg.mozilla.org/mozilla-central/rev/ba27bf696ecf
https://hg.mozilla.org/mozilla-central/rev/c1aed971a628
| Reporter | ||
Updated•7 months ago
|
Description
•