Closed Bug 1662681 Opened 4 years ago Closed 4 years ago

"Cross-site tracking cookies, and isolate remaining cookies" item is NOT displayed in the "Standard" section.

Categories

(Firefox :: Protections UI, defect)

Firefox 81
All
Unspecified
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox81 --- affected

People

(Reporter: obotisan, Unassigned)

References

Details

(Keywords: regressionwindow-wanted)

Affected versions

  • Firefox 81.0b5

Affected platforms

  • Windows 10.04 x64
  • Ubuntu 18.04 x64

Precondition

  • The following prefs are set in about:config:
    - privacy.firstparty.isolate = false

Steps to reproduce

  1. Navigate to about:preferences#privacy.
  2. Check the "Standard" section from about:preferences#privacy.

Expected result

  • "Cross-site tracking cookies, and isolate remaining cookies" item is displayed in the "Standard" section.

Actual result

  • "Cross-site tracking cookies, and isolate remaining cookies" item is NOT displayed in the "Standard" section.

Regression range

  • I will try to find the regression asap.

Notes

  • Nightly is not affected.

Suggested severity

  • S2
Has STR: --- → yes
QA Whiteboard: [qa-regression-triage]

At the moment only the has the option implemented. I am leaving this issue open until the fix is uplifted to Firefox beta.

We only enable this UI in Nightly, see here. So, I believe this is an expected behavior.

Arthur, could you confirm this? Thanks.

Flags: needinfo?(arthur)

by design: Bug 1631676 (see comment 25)
followup: Bug 1637344

Per our discussion, We don't want to make the dFPI as the default cookie behavior in the beta channel nor expose it. So, it is expected to not see "Cross-site tracking cookies, and isolate remaining cookies" in the "Standard" section. It is supposed to be "Cross-site tracking cookies".

Flags: needinfo?(arthur)

Thank you for the confirmation, Tim and Simon. We'll take account on this, when running the tests on Beta channel again.

I'm going to close this bug as per above comments.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.