1753586 - Fix navigator.cookieEnabled for dFPI

Status: RESOLVED FIXED

(Core :: Privacy: Anti-Tracking, defect, P2)

Description

[Tim Huang[:timhuang]]

Currently, navigator.cookieEnabled will return false in third-party contexts when dFPI is enabled. This behavior is incorrect because the cookie is still available in third-party contexts.

Also, we should still return true even the iframe is sandboxed given that the cookie is not disabled but throw a security error according to the WPT test.

We need to fix this in order to make the WPT cookie-enabled-noncookie-frame.html passing.

Comment 1

[Tim Huang[:timhuang]]

Attachment: Bug 1753586 - Navigator.cookieEnabled should return true when cookie is partitioned. r?smaug!,#anti-tracking-reviewers!

We change to return true for 'navigator.cookieEnabled' when the cookie
is partitioned. It did return false because the storage access is not
allowed in this case. But, acutally, we should return true because the
cookie is available.

Also, we should still return true in the case where accessing cookies
gets a security error, e.g. a sandboxed iframe. This behavior matches to
the spec.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/90571f6d8521
Navigator.cookieEnabled should return true when cookie is partitioned. r=smaug,anti-tracking-reviewers,pbz

Comment 3

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/90571f6d8521