1589276 - Don't forward nsIClassifiedChannel results via DocumentChannel

Status: RESOLVED FIXED

(Core :: Networking, enhancement, P2)

Description

[Matt Woodrow (:mattwoodrow)]

Currently DocumentChannelParent implements nsIParentChannel and forwards data immediately to the DocumentChannelChild so that it can implement nsIClassifiedChannel.

Ideally, we'd wait until we replace the DocumentChannel with the 'real' channel, and then only forward the classification updates a that point.

Similar to bug 1589275, this is because we won't always have a current DocumentChannelChild (like when the load was initiated by the parent process).

I tried doing this initially, and it failed tests, so we need to figure out why those fail. It may just be that the tests are relying on specific ordering of events (content blocking events vs the page load etc) and can be fixed easily.

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

[Matt Woodrow (:mattwoodrow)]

jya fixed this in bug 1588241.

Comment 3

[Chris Peterson [:cpeterson]]

(In reply to Matt Woodrow (:mattwoodrow) from comment #2)

jya fixed this in bug 1588241.

Retroactively assigning this bug to M4.1 because bug 1588241 blocks M4.1.