Closed
Bug 1843562
Opened 2 years ago
Closed 2 years ago
Ability to set Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy in a Web Extension
Categories
(WebExtensions :: Compatibility, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1750654
People
(Reporter: qfoiqnwrgoiwejfoq, Unassigned)
Details
Steps to reproduce:
In Chrome, one can make an extension cross-origin isolated by adding the following to manifest.json:
{
...
"cross_origin_embedder_policy": {
"value": "require-corp"
},
"cross_origin_opener_policy": {
"value": "same-origin"
},
...
}
I tried to do the same in Firefox.
Actual results:
It did not work
Expected results:
It should have worked. However, this is not supported on Firefox. I need to use SharedArrayBuffer, so I need cross-origin isolation.
|
Reporter | |
Comment 1•2 years ago
|
||
It would be good if it used the same API as chrome.
|
|
Reporter | |
Updated•2 years ago
|
Component: Untriaged → Compatibility
OS: Unspecified → All
Hardware: Unspecified → All
|
||
Updated•2 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1750654
Resolution: --- → DUPLICATE
|
|
Reporter | |
Comment 3•2 years ago
|
||
Sorry for creating a duplicate bug, I couldn’t find the already existing bug on the topic.
Summary: Ability to set Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy in a Web Extension → Sorry for creating a duplicate bug, I couldn’t find the already existing bug on the topic.
|
|
||
Updated•2 years ago
|
Summary: Sorry for creating a duplicate bug, I couldn’t find the already existing bug on the topic. → Ability to set Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy in a Web Extension
You need to log in
before you can comment on or make changes to this bug.
Description
•