<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>XS-Leaks on Nalar</title>
    <link>https://nalar.dev/tags/xs-leaks/</link>
    <description>Recent content in XS-Leaks on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/xs-leaks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cross-Origin-Opener-Policy Separates Window Relationships</title>
      <link>https://nalar.dev/cross-origin-opener-policy-separates-window-relationships/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/cross-origin-opener-policy-separates-window-relationships/</guid>
      <description>&lt;h1 id=&#34;cross-origin-opener-policy-separates-window-relationships&#34;&gt;Cross-Origin-Opener-Policy Separates Window Relationships&lt;/h1&gt;&#xA;&lt;p&gt;A browser window can hold a reference to another top-level window. &lt;code&gt;window.open()&lt;/code&gt; returns a &lt;code&gt;WindowProxy&lt;/code&gt;, and an opened document may receive a &lt;code&gt;window.opener&lt;/code&gt; reference. The same-origin policy restricts what cross-origin windows can inspect, but the relationship itself can still expose useful state and communication surfaces.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;Cross-Origin-Opener-Policy&lt;/code&gt; (COOP) adds a boundary around that relationship. The response header influences whether a top-level document remains in a compatible browsing context group (BCG) or moves into a new one. When policies require separate groups, references between opener and opened document are severed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
