Closed Bug 1336465 Opened 5 years ago Closed 5 years ago

[FirstPartyIsolation] Unable to login using Facebook on Sabah.com.tr

Categories

(Core :: DOM: Security, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox51 --- unaffected
firefox54 --- verified

People

(Reporter: bogdan_maris, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [tor][domsecurity-backlog2])

[Affected versions]:
- Firefox 52 beta 2
- latest Dev Edition 53.0a2
- latest Nightly 54.0a1

[Affected platforms]:
- macOS 10.12.2
- Ubuntu 16.04 32-bit
- Windows 10 64-bit

[Steps to reproduce]:
1. Visit Sabah.com.tr and login using Facebook

[Expected result]:
- Login is successful.

[Actual result]:
- User was not successfully logged in with Facebook account.

[Regression range]:
- This is not a regression.
Priority: -- → P2
Whiteboard: [tor] → [tor][domsecurity-backlog2]
Priority: P2 → P3
Hi Bogdan, 
Could you please set the preference "privacy.firstparty.isolate.restrict_opener_access" to be "false" and try it in Nightly 54.0a1 again? Thank you!
Flags: needinfo?(bogdan.maris)
(In reply to Cynthia Tang [:cynthiatang] from comment #1)
> Hi Bogdan, 
> Could you please set the preference
> "privacy.firstparty.isolate.restrict_opener_access" to be "false" and try it
> in Nightly 54.0a1 again? Thank you!

Bogdan,
Also we don't need to track this series of bugs for Firefox 52 and 53.
1. These are not actual bugs because the behavior in Firefox is correct (just not consistent with Tor).
2. The pref privacy.firstparty.isolate is off by default.  It does not affect normal users.

So, could you turn off the tracking flags status-firefox52 and status-firefox53 for these bugs?
Thanks.
(In reply to Cynthia Tang [:cynthiatang] from comment #1)
> Hi Bogdan, 
> Could you please set the preference
> "privacy.firstparty.isolate.restrict_opener_access" to be "false" and try it
> in Nightly 54.0a1 again? Thank you!

I tried again using latest Nightly across platforms and this time, the behavior of Fx with FPI matches Tor browser.

(In reply to Ethan Tseng [:ethan] from comment #2)
> (In reply to Cynthia Tang [:cynthiatang] from comment #1)
> > Hi Bogdan, 
> > Could you please set the preference
> > "privacy.firstparty.isolate.restrict_opener_access" to be "false" and try it
> > in Nightly 54.0a1 again? Thank you!
> 
> Bogdan,
> Also we don't need to track this series of bugs for Firefox 52 and 53.
> 1. These are not actual bugs because the behavior in Firefox is correct
> (just not consistent with Tor).
> 2. The pref privacy.firstparty.isolate is off by default.  It does not
> affect normal users.
> 
> So, could you turn off the tracking flags status-firefox52 and
> status-firefox53 for these bugs?
> Thanks.

You are right, I'll remove the tracking flags for 52 and 53.
Flags: needinfo?(bogdan.maris)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.