vulns.co
/
GKData.io MCP and API Buy me a coffee

WHATWG

HTML COOP: opener separation and same-origin authority

The HTML standard explains how opener policies separate browser windows during navigation. Breaking the opener connection does not fully isolate same-origin pages, which can still share storage, service workers, messaging and server responses. These are specified behaviors, not verified support in every browser or a substitute for application authorization.

Open the referenceTechnical StandardReviewed 2026-10-03

How to use this reference

Model window references separately from origin-wide data and service authority. For an owned application, document every shared client capability and server data path before relying on opener separation; combine appropriate embedding, cookie and response controls with an explicit trust-domain design.

Before reading

  • Browser origin and navigation concepts
  • HTTP session and response-cache fundamentals

Context and limits

  • A specification defines intended behavior; this review does not establish per-value support in deployed browsers.
  • Opener separation alone does not partition origin-wide storage or grant application-level authorization.
  • This resource complements message validation and request-context resources by modeling the isolation boundary itself.

Sources

  1. HTML Standard: Cross-origin opener policiesWHATWG · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software