Closed Bug 1575120 Opened 2 years ago Closed 7 months ago

Use DocumentChannel for non-http loads


(Core :: Networking, task, P2)




Fission Milestone Future


(Reporter: mattwoodrow, Assigned: mattwoodrow)


(Depends on 1 open bug, Blocks 1 open bug)


(Whiteboard: [necko-triaged])

Currently DocumentChannel is only setup for HTTP connections, but there's no reason we should need this to be the case.

I think we want it for all new document loads, so that we can easily switch processes to what we need for the origin.

Priority: -- → P2
Whiteboard: [necko-triaged]
Depends on: 1593560
Depends on: 1594166

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:


Fission Milestone: --- → ?
Depends on: 1598516
Depends on: 1598520
Depends on: 1598523

Tracking for Fission dogfooding (M5)

Fission Milestone: ? → M5
Depends on: 1612071

Matt says non-HTTP loads are almost done. Nika says non-HTTP loads should still block Fission dogfooding (M5).

Assignee: nobody → matt.woodrow

Print preview is one such non-HTTP protocol.

Matt says this doesn't need to block dogfooding.

Does this even need to block Fission? Tentatively block M7 Beta milestone so we review before Fission rides the trains.

Fission Milestone: M5 → M7
Depends on: 1644825
Depends on: 1647519
Fission Milestone: M7 → Future

All relevant load types which aren't very special (about:printpreview, about:crashcontent, and javascript: loads) are now using DocumentChannel. Closing this bug.

Closed: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.