Make sure test_ext_privacy.js doesn't depend on the default value of the network.cookie.cookieBehavior preference
Categories
(WebExtensions :: General, defect)
Tracking
(firefox64 fixed)
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Comment 5•6 years ago
|
||
bugherder |
Comment 6•6 years ago
|
||
Assignee | ||
Comment 7•6 years ago
|
||
Comment 9•6 years ago
|
||
Comment 10•5 years ago
|
||
Was this for desktop Firefox only, i.e. not supported on Android?
Comment 11•5 years ago
|
||
The compat-data doesn't break down cookieConfig
to provide information on its properties and therefore it doesn't provide any information about the values that behavior
can take. The reject_trackers
value is documented on privacy.websites, although there is no mention of the browser version it was introduced in, this would seem to be the extent to which we can document this feature.
Comment 12•5 years ago
|
||
The API is implemented in toolkit/, without any conditions, and the unit test from this bug is not skipped on Android. Therefore the extension API is available to Android.
The default value for the underlying preference was changed by the following bugs:
Bug 1492563 changed the default for cookieBehavior in Nightly on desktop.
Bug 1525727 changed the default for cookieBehavior on desktop for any desktop build.
Bug 1561385 changed the default for cookieBehavior on Android (also on Fennec because the patch was uplifted to the ESR68 branch).
I.e. on all currently supported release versions of Firefox, the default behavior is to deny tracking cookies.
(In reply to Richard Bloor from comment #11)
The compat-data doesn't break down
cookieConfig
to provide information on its properties and therefore it doesn't provide any information about the values thatbehavior
can take. Thereject_trackers
value is documented on privacy.websites, although there is no mention of the browser version it was introduced in, this would seem to be the extent to which we can document this feature.
You could add a "notes"
entry to the cookieConfig
entry in BCD to document the updated API.
Updated•5 years ago
|
Comment 13•5 years ago
|
||
Docs work is complete; see https://github.com/mdn/sprints/issues/2141 for a description of what we did. Please, can we have a review?
Comment 14•5 years ago
|
||
I see that the PR has been merged, but the note does still not show up on MDN at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/privacy/websites#Browser_compatibility
Comment 15•5 years ago
|
||
The release of BCD data usually happens on Thursdays (US time), and the deployment is usually later on the same day. This change should be included in this week's release/deployment. But, if it's not showing up by Friday, you need to do a shift-refresh while logged in.
Description
•