Closed
Bug 1316536
Opened 8 years ago
Closed 7 years ago
[FirstPartyIsolation] The publishing window will not disappear after clicking on "Publish" to publish news to your Facebook Wall
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1319773
Tracking | Status | |
---|---|---|
platform-rel | --- | - |
People
(Reporter: cynthiatang, Assigned: timhuang)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tor][domsecurity-active][platform-rel-Facebook][dfpi-ok])
This issue cannot be reproduced in Tor browser. Preference setting: 1. privacy.firstparty.isolate;true 2. network.predictor.enable-prefetch;false 3. network.predictor.enabled;false Step: 1. Launch Firefox browser 2. Go to http://www.teepr.com 3. Share news to your Facebook (1) Enter your account and password (2) Click on "Publish" to publish news to your Facebook Wall Actual result: - The publishing window will not disappear after clicking on "Publish" - Firefox with FPI : https://youtu.be/RqzenTkpw9Q - Firefox without FPI: https://youtu.be/v29SIeU0XbU Expected result: - The publishing window will disappear after clicking on "Publish" Firefox version: 52.0a1 (2016-10-27) (64-bit)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → tihuang
Updated•7 years ago
|
platform-rel: --- → ?
Whiteboard: [tor][domsecurity-active] → [tor][domsecurity-active][platform-rel-Facebook]
Updated•7 years ago
|
platform-rel: ? → -
Comment 1•7 years ago
|
||
I've also stumbled upon this using other websites (eg: Ebay-kleinanzeigen.de, Sabq.org, Onedio.com). Should I log new bugs for each website I find this issue? (more websites will probably suffer from the same issue once I finish testing)
Flags: needinfo?(tihuang)
Assignee | ||
Comment 2•7 years ago
|
||
I think we should file new bugs for each website for this issue. By doing so, it allows us to track this issue across different websites. And I think the root cause of this problem is as same as Bug 1319773, after it has been resolved we can test these websites to see this problem still exist or not. So I suggest you also making these bugs depend on Bug 1319773.
Flags: needinfo?(tihuang)
Reporter | ||
Comment 3•7 years ago
|
||
It works after disabling privacy.firstparty.isolate.restrict_opener_access
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Whiteboard: [tor][domsecurity-active][platform-rel-Facebook] → [tor][domsecurity-active][platform-rel-Facebook][dfpi-ok]
You need to log in
before you can comment on or make changes to this bug.
Description
•