Expose third-party cookie behavior pref in metrofx

RESOLVED WONTFIX

Status

Firefox for Metro
General
RESOLVED WONTFIX
5 years ago
4 years ago

People

(Reporter: jimm, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Windows 8.1

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [metro-mvp?])

(Reporter)

Description

5 years ago
The pref is 'network.cookie.cookieBehavior', and it looks like we don't have a default which means we accept all cookies, including from 3rd party advertisers (see bug 818340).

We should define this, and also we should consider adding a pref flyout option for it.

Updated

5 years ago
Blocks: 841214

Comment 1

5 years ago
Perhaps I'm missing something? Why would the default behavior on Metrofox be different from normal?
(Reporter)

Comment 2

5 years ago
(In reply to Tom Lowenthal [:StrangeCharm] from comment #1)
> Perhaps I'm missing something? Why would the default behavior on Metrofox be
> different from normal?

The default looks ok actually, I just checked and it's set to 3 in all.js. So this bug is more about offering the user a pref to change the default.
The default in libpref/src/init/all.js is network.cookie.cookieBehavior=3 ("limitForeign").  Metro Firefox uses this default, so we currently have the same default as desktop Firefox, which I think is what we want.

I think the only change we need to make (if any) is to add a visible pref for third-party cookie behavior in the Options flyout panel.
Summary: Define cookie behavior for metrofx → Expose third-party cookie behavior pref in metrofx

Comment 4

5 years ago
We are not adding cookie management to Metro Firefox any time soon.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
No longer blocks: 841214
(Assignee)

Updated

4 years ago
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.