Closed
Bug 1309816
Opened 7 years ago
Closed 6 years ago
Some firstPartyDomains are empty
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1312954
People
(Reporter: cynthiatang, Assigned: cynthiatang)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tor][domsecurity-active][dfpi-ok])
This issue can be reproduced in Non-e10s and e10s Default search engine: Google Step: 1. Clear all History and Cookies 1. Launch Firefox browser 2. Go to paypal.com, wikipedia.org, qq.com, twitter.com or ... 3. Click on the Add-ons “Cookies Manager +” to view the originAttributes Actual result: - Video: https://youtu.be/n-2vXn47bMo - Some firstPartyDomains are empty Expected result: - The firstPartyDomain should not be empty. Firefox version: 52.0a1 (2016-10-11) (64-bit)
Comment 1•7 years ago
|
||
Tim, please help to investigate this bug, thanks.
Flags: needinfo?(tihuang)
Priority: -- → P1
Comment 2•7 years ago
|
||
We had tested this with disabling the network predictor. The result shows that no cookie of empty firstPartyDomain been set for certain websites, which means disabling network predictor fixes this issue. But Cynthia will run a full test of top 100 websites to verify this.
Flags: needinfo?(tihuang)
Assignee | ||
Comment 3•7 years ago
|
||
Some firstPartyDomains are still empty after disabling "network.predictor.enable-prefetch" and "network.predictor.enabled". Test report: https://goo.gl/UmyN10 After Bug 1305592 is resolved, I will verify this issue again. Thanks.
Depends on: 1305592
Updated•7 years ago
|
Priority: P1 → P2
Updated•7 years ago
|
Comment 4•6 years ago
|
||
Once bug 1312954 was resolved, this bug should be fixed even if network.predictor preferences are not turned off.
Comment 5•6 years ago
|
||
Cynthia, could you verify this bug based on comment 4?
Flags: needinfo?(ctang)
Assignee | ||
Comment 6•6 years ago
|
||
Hi Ethan, I finished the testing. It works well. Thanks. Test report: https://goo.gl/4yjqE2 Firefox version: 54.0a1 (2017-02-06) (64-bit) Preference & Setting: 1. privacy.firstparty.isolate = true 2. network.predictor.enable-prefetch = false 3. network.predictor.enabled = false 4. privacy.firstparty.isolate.restrict_opener_access = false 5. Disable Safe Browsing (Enter "about:preferences#security" in URL field and unselect "Block dangerous and deceptive content")
Flags: needinfo?(ctang)
Comment 7•6 years ago
|
||
(In reply to Cynthia Tang [:cynthiatang] from comment #6) > Hi Ethan, > I finished the testing. It works well. Thanks. > Test report: https://goo.gl/4yjqE2 Cynthia, thank you for performing the verification! Cheers!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Whiteboard: [tor][domsecurity-active] → [tor][domsecurity-active][dfpi-ok]
You need to log in
before you can comment on or make changes to this bug.
Description
•