Assuming I am understanding this correctly, it appears from this doc
https://developer.mozilla.org/en-US/docs/Supporting_per-window_private_browsing
that they maybe disabled in some instances of private browsing given changes in
Fx 20.
> Forcing a channel into private mode
>
> Usually, network channels inherit the privacy status of the document that
> created them, which means that they work correctly most of the time. However,
> sometimes you need to adjust the privacy status on a channel manually, for
> example, if you have created the channel directly yourself. You can use the
> nsIPrivateBrowsingChannel interface for this purpose. The example below
> creates a channel to load a URL, and forces it to be in private mode.
>
> var channel = Services.io.newChannel("http://example.org";, null, null);
>
> channel
> .QueryInterface(Components.interfaces.nsIPrivateBrowsingChannel);
>
> channel
> .setPrivate(true); // force the channel to be loaded in private mode
> Similarly, XMLHttpRequest objects created via
> createInstance(Ci.nsIXMLHttpRequest) will often require explicit adjustment,
> since they have no context from which to derive a privacy status.
>
> var xhr =
> Components.classes["@mozilla.org/xmlextras/xmlhttprequest;1"].createInstance(Components.interfaces.nsIXMLHttpReqeust);
> var channel =
> xhr.channel.QueryInterface(Components.interfaces.nsIPrivateBrowsingChannel);
>
> channel
> .setPrivate(true);
On 16 May, 2014, at 09:39 AM, Tim Taubert <[email protected]> wrote:
> Curtis Koenig wrote:
>> Would this be disabled in Private Browsing? If not that might be perceived
>> as negating one of the reasons users have for using that particular feature.
>
> Are sync XHRs and HTTP redirects disabled in private browsing? :)
>
> - Tim
--
Curtis
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
