From a2c8ae5cc56850838e05a332454b694a6f0b9ef6 Mon Sep 17 00:00:00 2001
From: Stefan Zager <szager@chromium.org>
Date: Mon, 11 Apr 2022 12:20:11 -0700
Subject: [PATCH] Clarify same-domain-target designation for explicit root
 observers

Based on:

https://github.com/w3c/IntersectionObserver/pull/483
---
 index.bs | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 4ce22a3..e4dd343 100644
--- a/index.bs
+++ b/index.bs
@@ -200,9 +200,7 @@ a <a>target</a> whose <a>relevant settings object</a>'s <a>origin</a> is
 <a>same origin-domain</a> with the <a>top-level origin</a>, referred to as a
 <dfn for="IntersectionObserver">same-origin-domain target</dfn>;
 as opposed to a <dfn for="IntersectionObserver">cross-origin-domain target</dfn>.
-Any <a>target</a> of an <a>explicit root observer</a> is also a <a>same-origin-domain target</a>,
-since the <a>target</a> must be in the same <a>document</a> as the
-<a>intersection root</a>.
+Any <a>target</a> of an <a>explicit root observer</a> is treated as a <a>same-origin-domain target</a>.
 
 Note: In {{MutationObserver}}, the {{MutationObserverInit}} options are passed
 to {{MutationObserver/observe()}} while in {{IntersectionObserver}} they are