Closed Bug 1635145 Opened 5 years ago Closed 4 years ago

The button changes to "Signed in" with certain settings (Custom mode - All third-party cookies)

Categories

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

77 Branch
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox-esr68 --- unaffected
firefox75 --- unaffected
firefox76 --- disabled
firefox77 --- disabled
firefox78 --- wontfix

People

(Reporter: obotisan, Unassigned)

References

Details

(Keywords: regression)

Affected versions

  • Firefox 77.0a1

Affected platforms

  • Windows 10 x64
  • macOS 10.15

Steps to reproduce

  1. Reach about:preferences#privacy and Set the Custom option:
    • Tracking Content - In all windows
    • Cookies - All third-party cookies (may cause websites to break)
  2. Reach https://senglehardt.com/test/identity_providers/google.html and Click the Sign in Prompt.
  3. Provide a valid email address and a password then sign in.

Expected result

  • The google button string remains unchanged "Sign in".

Actual result

  • The google button string is changed to "Signed in".

Regression range

  • This is a recent regression, because I can't reproduce the issue on Firefox 76.0.
Has Regression Range: --- → no
Has STR: --- → yes

I can't reproduce this on the latest Nightly 78.0a1. Maybe this was fixed. Could you check again with the latest Nightly?

Flags: needinfo?(oana.botisan)

I can still reproduce the issue using Nightly 78.0a1 (2020-05-05) on Windows 10 x64.

Flags: needinfo?(oana.botisan)

The regression window points to code that landed in 76 but the comment #0 says that 76 is not affected. Is it a nightly-only regression?

Flags: needinfo?(rares.doghi)

Oh great, I figured out what's going on here. Right now, we've enabled the heuristic for rejecting third-party cookies in Nightly. So, the third-party cookies would be accessible in this test case since the heuristic will be triggered. So, "Signed in" is expected here in Nightly, but only in Nightly.

The good news is that this heuristic is put behind a pref "network.cookie.rejectForeignWithExceptions.enabled". Could you turn this pref off and try it again?

With this pref network.cookie.rejectForeignWithExceptions.enabled set to false i was unable to reproduce this issue at all.

Flags: needinfo?(rares.doghi)

Thanks, marking as disabled for beta and release.

This behavior is expected in Nightly. And we can resolve this issue by turn the pref "network.cookie.rejectForeignWithExceptions.enabled" off. Resolve this as WFM.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME

Sorry, Resolve Invalid is more appropriate.

Resolution: WORKSFORME → INVALID
You need to log in before you can comment on or make changes to this bug.