Closed
Bug 1555859
Opened 5 years ago
Closed 5 years ago
Partitioning of IDB in the third-party context doesn't always work correctly
Categories
(Core :: Privacy: Anti-Tracking, defect)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
(Blocks 1 open bug)
Details
I see a storage/default/https+++tpc.googlesyndication.com/idb
directory getting created in the profile after a bit of browsing around...
Assignee | ||
Comment 1•5 years ago
|
||
I think this can be reproduced on https://www.vulture.com/2019/05/john-candy-steve-martin-wild-crazy-guys-book-excerpt.html?utm_source=pocket-newtab. The IDB in question comes from https://tpc.googlesyndication.com/safeframe/1-0-33/html/container.html on that page.
Assignee | ||
Comment 2•5 years ago
|
||
In the parent process, inside FactoryOp::OpenDirectory()
, looking at mCommonParams.principalInfo_
, the first party domain field on the OA is empty...
Assignee | ||
Comment 3•5 years ago
|
||
I failed to finish filing this bug. :-(
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•