Cross-Origin-Opener-Policy
Controls whether a document shares a browsing context group with cross-origin documents.
Support in current browsers
Checked against the current browser versions recorded in MDN browser data 8.0.7.
| Browser | Minimum | Outcome | Reason |
|---|---|---|---|
| Chrome | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Edge | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari | 26.5 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Chrome for Android | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox for Android | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari on iOS | 26.5 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Android WebView | 150 | Not supported | At least one required mapped feature is not available at this browser baseline. |
| Samsung Internet | 29.0 | Works | Every required mapped BCD feature is available without a recorded qualification. |
What this feature can and cannot do
Helps protect against
- Cross-window reference attacks
- Cross-origin process isolation gaps
Does not guarantee
- All cross-origin data exposure
- Application authorisation
- Isolation without companion resource policies
What you need before using it
- Popup and integration compatibility review
Fallback to keep in place
Use defensive opener handling and explicit cross-origin communication checks.