Closed
Bug 1713670
Opened 3 years ago
Closed 3 years ago
Revisit browser_navigateEvents.js to watch for DOCUMENT_EVENT in addition/place of target navigation events
Categories
(DevTools :: Framework, task)
DevTools
Framework
Tracking
(Fission Milestone:MVP, firefox92 fixed)
Tracking | Status | |
---|---|---|
firefox92 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(1 file, 1 obsolete file)
(deleted),
text/x-phabricator-request
|
Details |
This test would be a nice one to augment in order to better cover the various navigation events used in bug 1702511.
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•3 years ago
|
||
This test fails with server side targets. But my WIP is having race conditions... and still rely on target navigate events which stop working with server targets.
Blocks: 1698891
Assignee | ||
Updated•3 years ago
|
Whiteboard: dt-fission-m3-triage
Updated•3 years ago
|
Fission Milestone: --- → MVP
Whiteboard: dt-fission-m3-triage → dt-fission-m3-mvp
Assignee | ||
Comment 3•3 years ago
|
||
target actor's will-navigate and navigate is no longer fired with server targets.
These two tests are still asserting them, so disable server target in these two tests.
We should probably remove them once we drop the server target preference (bug 1721852).
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2bec13a6e23b
[devtools] Disable server targets in tests covering client targets. r=nchevobbe
Comment 5•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox92:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
Updated•3 years ago
|
Attachment #9224350 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•