Closed Bug 1715904 Opened 3 years ago Closed 3 years ago

Use DOCUMENT_EVENT's will-navigate event in all tests

Categories

(DevTools :: Framework, task)

task

Tracking

(Fission Milestone:M8, firefox91 fixed)

RESOLVED FIXED
91 Branch
Fission Milestone M8
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.

Blocks: 1715905

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.

Component: General → Framework
Fission Milestone: --- → M8
Whiteboard: dt-fission-m3-triage → dt-fission-m3-mvp
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED

This can actually be helpful also in production.
See netmonitor's connector and TargetCommand.reload.

I'm wondering if we should have yet another helper, like TargetCommand.waitForNextWillNavigate,
which would be a wrapper around waitForNextResource ?

Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8f9522b3c4c8 [devtools] Move waitForNextResource from test helper to ResourceCommand. r=nchevobbe https://hg.mozilla.org/integration/autoland/rev/2b1d4ef5f3ea [devtools] Refactor test to use DOCUMENT_EVENT's will-navigate. r=nchevobbe
Regressions: 1717460
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: