Skip to content

Commit

Permalink
Editorial tweaks
Browse files Browse the repository at this point in the history
  • Loading branch information
domenic committed Aug 14, 2019
1 parent 73622c5 commit 86c1d70
Showing 1 changed file with 12 additions and 11 deletions.
23 changes: 12 additions & 11 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -78164,6 +78164,7 @@ dictionary <dfn>DragEventInit</dfn> : <span>MouseEventInit</span> {
<ol>
<li><p>Let <var>browsingContext</var> be the result of <span>creating a new browsing
context</span> with <var>element</var>'s <span>node document</span>, and <var>element</var>'s
<span>node document</span>'s <span data-x="concept-document-bc">browsing context</span>'s
<span>top-level browsing context</span>'s <span data-x="tlbc group">group</span>.</p></li>

<li><p>Set <var>element</var>'s <span>nested browsing context</span> to
Expand Down Expand Up @@ -90318,9 +90319,9 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
data-x="concept-global-object-realm">realms</span> that can synchronously access each other, and
thus needs to run in a single execution thread.</p>

<p class="note">Two <code>Window</code> objects that have the same <span>agent</span> does not
<p class="note">Two <code>Window</code> objects having the same <span>agent</span> does not
indicate they can directly access all objects created in each other's realms. They would have to
be in <span>same origin-domain</span>, see <span>IsPlatformObjectSameOrigin</span>.</p>
be <span>same origin-domain</span>; see <span>IsPlatformObjectSameOrigin</span>.</p>

<p>Until such a time that this standard has a better handle on lifetimes, it defines four types of
<span data-x="agent">agents</span> that user agents must allocate at the appropriate time.</p>
Expand Down Expand Up @@ -90374,6 +90375,13 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
in particular among which <span data-x="agent">agents</span> the backing data of
<code>SharedArrayBuffer</code> objects can be shared.</p>

<p class="note">Conceptually, the <span>agent cluster</span> concept is an
architecture-independent, idealized "process boundary" that groups together multiple "threads"
(<span data-x="agent">agents</span>). The <span data-x="agent cluster">agent clusters</span>
defined by the specification are generally more restrictive than the actual process boundaries
implemented in user agents. By enforcing these idealized divisions at the specification level, we
ensure that web developers see interoperable behavior with regard to shared memory, even in the
face of varying and changing user agent process models.</p>
<p>A <dfn data-export="">scheme-and-site</dfn> is a <span>tuple</span> of a <span
data-x="concept-url-scheme">scheme</span> and a <span data-x="concept-domain">domain</span>.</p>

Expand Down Expand Up @@ -90414,8 +90422,8 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
<p>A <dfn data-export="">similar-origin window agent</dfn> is an <span>agent</span> whose
[[CanBlock]] is false. </p>

<p class="note">All global objects that use this agent all have the a similar <span>origin</span>
and are allocated via the <span data-x="obtain-similar-origin-window-agent">obtain similar-origin
<p class="note">All global objects that use this agent all have a similar <span>origin</span> and
are allocated via the <span data-x="obtain-similar-origin-window-agent">obtain similar-origin
window agent</span> algorithm.</p>

<p>To <dfn data-x="obtain-browsing-agent-cluster">obtain a browsing context agent cluster</dfn>,
Expand All @@ -90438,13 +90446,6 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
<li><p>Return <var>group</var>'s <span>agent cluster map</span>[<var>key</var>].</p></li>
</ol>

<p class="note">Conceptually, the <span>agent cluster</span> concept is an
architecture-independent, idealized "process boundary" that groups together multiple "threads"
(<span data-x="agent">agents</span>). The <span data-x="agent cluster">agent clusters</span>
defined by the specification are generally more restrictive than the actual process boundaries
implemented in user agents. By enforcing these idealized divisions at the specification level, we
ensure that web developers see interoperable behavior with regard to shared memory, even in the
face of varying and changing user agent process models.</p>

<p>A <span>similar-origin window agent</span>, <span>dedicated worker agent</span>, <span>shared
worker agent</span>, or <span>service worker agent</span>, <var>agent</var>, <span>can share
Expand Down

0 comments on commit 86c1d70

Please sign in to comment.