Skip to content

Commit

Permalink
Editorial: inline noreferrer processing model
Browse files Browse the repository at this point in the history
  • Loading branch information
annevk committed Feb 12, 2019
1 parent 8cc0721 commit f47773d
Showing 1 changed file with 15 additions and 17 deletions.
32 changes: 15 additions & 17 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -23269,13 +23269,18 @@ document.body.appendChild(wbr);</code></pre>

<li><p>If there is a <var>hyperlink suffix</var>, append it to <var>URL</var>.</p></li>

<li><p>Let <var>resource</var> be a new <span data-x="concept-request">request</span> whose <span
<li><p>Let <var>request</var> be a new <span data-x="concept-request">request</span> whose <span
data-x="concept-request-url">url</span> is <var>URL</var> and whose <span
data-x="concept-request-referrer-policy">referrer policy</span> is the current state of
<var>subject</var>'s <code data-x="">referrerpolicy</code> content attribute.</p></li>

<li id="noreferrer-a-area-processing-model"><p>If <var>subject</var>'s <a href="#linkTypes">link
types</a> includes the <code data-x="rel-noreferrer">noreferrer</code> keyword, then set
<var>request</var>'s <span data-x="concept-request-referrer">referrer</span> to "<code
data-x="">no-referrer</code>".</p></li>

<li><p><span>Queue a task</span> to <span>navigate</span><!--DONAV hyperlink--> the
<var>target</var> <span>browsing context</span> to <var>resource</var>. If <var>replace</var> is
<var>target</var> <span>browsing context</span> to <var>request</var>. If <var>replace</var> is
true, the navigation must be performed with <span>replacement enabled</span>. The
<span>source browsing context</span> must be <var>source</var>.</p></li>

Expand Down Expand Up @@ -24579,7 +24584,7 @@ document.body.appendChild(wbr);</code></pre>
context</span>. E.g., its <code data-x="dom-opener">window.opener</code> attribute will be
null.</p>

<p w-nodev class="note">See also the <a href="#noopener">processing model</a> where the branching
<p w-nodev class="note">See also the <a href="#noopener">processing model</a> where the branching
between an <span>auxiliary browsing context</span> and a <span>top-level browsing context</span>
is defined.</p>

Expand Down Expand Up @@ -24609,24 +24614,17 @@ document.body.appendChild(wbr);</code></pre>
data-x="hyperlink annotation">annotates</span> any other hyperlinks created by the element (the
implied hyperlink, if no other keywords create one).</p>

<p>It indicates that no referrer information is to be leaked when following the link.</p>
<p>It indicates that no referrer information is to be leaked when following the link and also
implies the <code data-x="rel-noopener">noopener</code> keyword behavior under the same
conditions.</p>

<div w-nodev>
<p w-nodev class="note">See also the <a href="noreferrer-a-area-processing-model">processing
model</a> where referrer is directly manipulated.</p>

<p>If a user agent follows a link defined by an <code>a</code> or <code>area</code> element that
has the <code data-x="rel-noreferrer">noreferrer</code> keyword, the user agent must set their
<span data-x="concept-request">request</span>'s <span
data-x="concept-request-referrer">referrer</span> to "<code data-x="">no-referrer</code>".</p>

<p class="note">For historical reasons, the <code data-x="rel-noreferrer">noreferrer</code>
keyword implies the behavior associated with the <code data-x="rel-noopener">noopener</code>
keyword when present on a hyperlink that <span data-x="creating a new browsing
context">creates</span> a new <span>browsing context</span>. That is, <code data-x="">&lt;a
href="..." rel="noreferrer" target="_blank"&gt;</code> has the same behavior as <code
<p class="example"><code data-x="">&lt;a href="..." rel="noreferrer" target="_blank"&gt;</code>
has the same behavior as <code
data-x="">&lt;a href="..." rel="noreferrer noopener" target="_blank"&gt;</code>.</p>

</div>


<h5>Link type "<dfn><code data-x="rel-opener">opener</code></dfn>"</h5>

Expand Down

0 comments on commit f47773d

Please sign in to comment.