Closed
Bug 1610317
Opened 4 years ago
Closed 1 year ago
Use "SpecialPowers.spawn" instead of "ContentTask.spawn" in browser chrome tests for CDP
Categories
(Remote Protocol :: CDP, task, P3)
Remote Protocol
CDP
Tracking
(firefox113 fixed)
RESOLVED
FIXED
113 Branch
| Tracking | Status | |
|---|---|---|
| firefox113 | --- | fixed |
People
(Reporter: whimboo, Assigned: ofrazy, Mentored)
References
Details
(Whiteboard: [lang=js])
Attachments
(1 file)
For Fission compatibility ContentTask.spawn() shouldn't be used. Right now it's necessary because we have to track the webprogress listener across an ongoing page load.
We have to find an alternative for determining the docShell's load flags.
|
||
Updated•4 years ago
|
Fission Milestone: --- → M6c
|
||
Comment 1•4 years ago
|
||
Removing the use of ContentTask.spawn here shouldn't block Fission, so moving to Future.
Fission Milestone: M6c → Future
|
||
Updated•3 years ago
|
Component: CDP: Network → CDP
|
Reporter | |
Comment 2•2 years ago
|
||
Here a link that references tests that still make use of ContentTask.spawn():
https://searchfox.org/mozilla-central/search?q=ContentTask.spawn&path=remote%2F&case=false®exp=false
Mentor: hskupin
Whiteboard: [lang=js]
|
|
Reporter | |
Updated•2 years ago
|
Fission Milestone: Future → ---
|
||
Updated•2 years ago
|
Severity: normal → S3
|
|
Reporter | |
Updated•1 year ago
|
Summary: Use "SpecialPowers.spawn" instead of "ContentTask.spawn" in remote/test/browser/network/browser_setCacheDisabled.js → Use "SpecialPowers.spawn" instead of "ContentTask.spawn" in browser chrome tests for CDP
|
|
Reporter | |
Comment 4•1 year ago
|
||
Yes, please do so. As long as there is no assignee for the bug you can get started. Once a patch is uploaded we consider a bug as taken. Thanks!
|
||
Updated•1 year ago
|
Assignee: nobody → ofrazy
Status: NEW → ASSIGNED
|
|
||
Updated•1 year ago
|
Attachment #9322673 -
Attachment description: Bug 1610317 - use SpecialPowers.spawn instead of ContentTask.spawn in browser chrome tests for CDP → Bug 1610317 - [cdp] Use SpecialPowers.spawn instead of ContentTask.spawn in browser chrome tests.
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ec774797366e [cdp] Use SpecialPowers.spawn instead of ContentTask.spawn in browser chrome tests. r=webdriver-reviewers,whimboo
|
||
Comment 7•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•