Storage Partitioning
Categories
(WebExtensions :: General, defect)
Tracking
(Not tracked)
People
(Reporter: itay, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Linux; Android 11; SM-N9860) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Mobile Safari/537.36
Steps to reproduce:
we created a firefox addon that displays user quick launch bar on each web page he visits. this is implemented by contect scripts that creates an iframe pointing to some page from our wev add on e.g. url origin is moz-extension://...
Actual results:
storage is partitioned between iframes that our running on different origin top level pages
Expected results:
iframe serving pages from moz-extension protocol should be excluded from storage partitioning just like chrome and safaro do
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug is invalid.
If you think the bot is wrong, please reopen the bug and move it back to its prior component.
If your bug description is written in a non-English language, please use Google Translate or a similar service to translate it.
Please note that this is a production bug database used by the Mozilla community to develop Firefox, Thunderbird and other products.
Filing test bugs here will waste the time of our contributors, volunteers and employees.
Accounts that abuse bugzilla.mozilla.org will be disabled.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:zombie, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
|
||
What is specifically broken for you, and what is your use case exactly? Can you provide a minimal extension and STR please?
Comment 4•2 years ago
|
||
Closing bug because we haven't received a response.
Note: top-level moz-extension:-documents are already exempt from storage partitioning, but moz-extension:
documents in iframes are not. Storage partitioning is designed to be keyed by the top-level document, and it would require a strong motivation before we'd even consider adding an exception for that behavior for extensions.
Extensions that want to opt in to sharing specific cookies can use the cookies
API to copy cookies from one to another, see partitionKey
and the documentation at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/cookies#storage_partitioning
Description
•