Skip to content

Commit a2c8ae5

Browse files
Clarify same-domain-target designation for explicit root observers
Based on: #483
1 parent cc4d964 commit a2c8ae5

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

index.bs

+1-3
Original file line numberDiff line numberDiff line change
@@ -200,9 +200,7 @@ a <a>target</a> whose <a>relevant settings object</a>'s <a>origin</a> is
200200
<a>same origin-domain</a> with the <a>top-level origin</a>, referred to as a
201201
<dfn for="IntersectionObserver">same-origin-domain target</dfn>;
202202
as opposed to a <dfn for="IntersectionObserver">cross-origin-domain target</dfn>.
203-
Any <a>target</a> of an <a>explicit root observer</a> is also a <a>same-origin-domain target</a>,
204-
since the <a>target</a> must be in the same <a>document</a> as the
205-
<a>intersection root</a>.
203+
Any <a>target</a> of an <a>explicit root observer</a> is treated as a <a>same-origin-domain target</a>.
206204

207205
Note: In {{MutationObserver}}, the {{MutationObserverInit}} options are passed
208206
to {{MutationObserver/observe()}} while in {{IntersectionObserver}} they are

0 commit comments

Comments
 (0)