Per-window Private Browsing: Difference between revisions

Jump to navigation Jump to search
Line 49: Line 49:


=== Channels ===
=== Channels ===
The design which requires access to docshells is fundamentally broken for e10s, where networking occurs in the parent process and the relevant docshell is in a content process. [http://hg.mozilla.org/users/josh_joshmatthews.net/pb-per-window/file/352685cd7155/pb-httpchannel
The design which requires access to docshells is fundamentally broken for e10s, where networking occurs in the parent process and the relevant docshell is in a content process. [http://hg.mozilla.org/users/josh_joshmatthews.net/pb-per-window/file/352685cd7155/pb-httpchannel This patch] demonstrates a correct implementation for HTTP channels, whereby a concrete nsHttpChannel object can be reliably queried as to its PB usage, regardless of process. Possible solutions:
This patch] demonstrates a correct implementation for HTTP channels, whereby a concrete nsHttpChannel object can be reliably queried as to its PB usage, regardless of process. Possible solutions:


* add a new interface (or modify nsIChannel) to add private browsing status to every channel type, and propagate the information from the child to the parent as in the previously-linked HTTP patch
* add a new interface (or modify nsIChannel) to add private browsing status to every channel type, and propagate the information from the child to the parent as in the previously-linked HTTP patch
Confirmed users
512

edits

Navigation menu