<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>COOP on Nalar</title>
    <link>https://nalar.dev/tags/coop/</link>
    <description>Recent content in COOP on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/coop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cross-Origin Opener Policy Separates Window Relationships at the Browsing Context Boundary</title>
      <link>https://nalar.dev/cross-origin-opener-policy-separates-window-relationships-at-the-browsing-context-boundary/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/cross-origin-opener-policy-separates-window-relationships-at-the-browsing-context-boundary/</guid>
      <description>&lt;h1 id=&#34;cross-origin-opener-policy-separates-window-relationships-at-the-browsing-context-boundary&#34;&gt;Cross-Origin Opener Policy Separates Window Relationships at the Browsing Context Boundary&lt;/h1&gt;&#xA;&lt;p&gt;A browser can prevent a cross-origin popup from reading most properties of its opener and still preserve a live relationship between the two windows. The same-origin policy restricts direct access to a foreign document, but a cross-origin &lt;code&gt;WindowProxy&lt;/code&gt; can remain reachable, expose a limited interface, participate in navigation relationships, and carry observable state such as whether the referenced window is closed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
