Add support for 3rdPartyFrameStorage permission and the frame-only Storage Access API to GeckoView
Categories
(Core :: Privacy: Anti-Tracking, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox121 | --- | fixed |
People
(Reporter: bvandersloot, Assigned: bvandersloot)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This will involve enabling the frame only Storage Access API permission and making changes to the permissions in GeckoView to support the new permission that appears. The hard part here is the general weirdness between having two permissions that have identical semantics the user (because of their privacy properties), but maybe not the developer.
One approach would be to have the "storage-access" refer to specifically the 3rdPartyFrameStorage internal permission and a new type for the 3rdPartyStorage internal permission. This would leave dealing with the UI implications of both being set to the consumer, which may be the right tradeoff. The diff for this approach would closely follow some parts of the fix for Bug 1543720, where we added the "storage-access" permission to GeckoView.
Assignee | ||
Comment 1•1 years ago
|
||
Updated•1 years ago
|
Assignee | ||
Updated•1 years ago
|
Updated•1 years ago
|
Comment 3•1 year ago
|
||
bugherder |
Description
•