Use DOCUMENT_EVENT's will-navigate event in all tests
Categories
(DevTools :: Framework, task)
Tracking
(Fission Milestone:M8, firefox91 fixed)
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(2 files)
Bug 1712592 introduced DOCUMENT_EVENT will-navigate resource in order to replace target's will-navigate event.
Many tests are still listening to target actor's will-navigate,
they should instead listen ot DOCUMENT_EVENT will-navigate which is more resilient when a cross process navigation / target switching happens.
This blocks bug 1698891, as server side targets stop emitting will-navigate.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Framework' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
This can actually be helpful also in production.
See netmonitor's connector and TargetCommand.reload.
Assignee | ||
Comment 3•3 years ago
|
||
I'm wondering if we should have yet another helper, like TargetCommand.waitForNextWillNavigate,
which would be a wrapper around waitForNextResource ?
Comment 5•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8f9522b3c4c8
https://hg.mozilla.org/mozilla-central/rev/2b1d4ef5f3ea
Description
•