820304 - Remove e10s logic for supporting nsIPrivateBrowsingChannel

Status: NEW

(Core :: Networking, defect, P5)

Description

[Jason Duell]

As discussed with Ehsan, now that we require all child channels to pass in a TabParent & a LoadContext, we shouldn't need nsIPrivateBrowsingChannel support in e10s since that's only used for channels that lack a loadContext.

This would cleanup the IPDL code a bit, and make it easier for us to eventually hopefully get rid of nsIPrivateBrowsingChannel completely.  We definitely don't want to encourage its use.

The only reason to keep is it we plan to move something that's currently in parent (favicon service is the main one IIRC) to a non-content child process.  That seems unlikely.

Not a B2G blocker.

Comment 1

[Jason Duell]

see attachment 689879 [details] in bug 782542 for IRC chat with ehsan about this.

Comment 2

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 3

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 4

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.