1575120 - Use DocumentChannel for non-http loads

Status: RESOLVED FIXED

(Core :: Networking, task, P2)

Description

[Matt Woodrow (:mattwoodrow)]

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.

Comment 1

[Chris Peterson [:cpeterson]]

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:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Comment 2

[Chris Peterson [:cpeterson]]

Tracking for Fission dogfooding (M5)

Comment 3

[Chris Peterson [:cpeterson]]

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

Comment 4

[Chris Peterson [:cpeterson]]

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.

Comment 5

[Nika Layzell [:nika] (ni? for response)]

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