<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>COEP on Nalar</title>
    <link>https://nalar.dev/tags/coep/</link>
    <description>Recent content in COEP on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/coep/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>COOP and COEP Turn Cross-Origin Isolation into a Document-Group Boundary</title>
      <link>https://nalar.dev/coop-and-coep-turn-cross-origin-isolation-into-a-document-group-boundary/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/coop-and-coep-turn-cross-origin-isolation-into-a-document-group-boundary/</guid>
      <description>&lt;h1 id=&#34;coop-and-coep-turn-cross-origin-isolation-into-a-document-group-boundary&#34;&gt;COOP and COEP Turn Cross-Origin Isolation into a Document-Group Boundary&lt;/h1&gt;&#xA;&lt;p&gt;A web page can be same-origin with its own application code while still maintaining relationships with cross-origin popups, frames, workers, and resources. Those relationships matter when a browser decides which documents can occupy the same browsing context group and which capabilities can be exposed safely.&lt;/p&gt;&#xA;&lt;p&gt;Cross-origin isolation changes that arrangement through two response policies with different jobs. &lt;code&gt;Cross-Origin-Opener-Policy&lt;/code&gt; (COOP) controls top-level opener relationships and browsing context group switches. &lt;code&gt;Cross-Origin-Embedder-Policy&lt;/code&gt; (COEP) constrains the cross-origin resources a document and its descendants may load. Used together in the configuration required for isolation, they establish a browser-enforced boundary that is broader than the same-origin policy alone.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
