[html5] r8307 - [giow] (2) Fix the rules on what 'Origin' header to use when navigating to a res [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Nov 22 10:48:58 PST 2013
Author: ianh
Date: 2013-11-22 10:48:56 -0800 (Fri, 22 Nov 2013)
New Revision: 8307
Modified:
complete.html
index
source
Log:
[giow] (2) Fix the rules on what 'Origin' header to use when navigating to a resource in an <iframe>, <object>, <embed>, or <frame> element, so that the latter two are not forgotten.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23837
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2013-11-21 23:48:58 UTC (rev 8306)
+++ complete.html 2013-11-22 18:48:56 UTC (rev 8307)
@@ -298,7 +298,7 @@
<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 21 November 2013</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 22 November 2013</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -66791,9 +66791,10 @@
potentially http-origin privacy sensitive -->
<p>Otherwise, if the <a href=#browsing-context>browsing context</a> being navigated is a <a href=#child-browsing-context>child browsing
- context</a> for an <code><a href=#the-iframe-element>iframe</a></code> or <code><a href=#the-object-element>object</a></code> element, then the <a href=#fetch title=fetch>fetching algorithm</a> must be invoked from the <code><a href=#the-iframe-element>iframe</a></code> or
- <code><a href=#the-object-element>object</a></code> element's <a href=#browsing-context-scope-origin>browsing context scope origin</a>, if it has one.</p>
- <!-- potentially http-origin privacy sensitive -->
+ context</a>, then the <a href=#fetch title=fetch>fetching algorithm</a> must be invoked from the
+ <a href=#browsing-context-scope-origin>browsing context scope origin</a> of the <a href=#browsing-context-container>browsing context container</a> of the
+ <a href=#browsing-context>browsing context</a> being navigated, if it has one.</p> <!-- potentially http-origin
+ privacy sensitive -->
</li>
Modified: index
===================================================================
--- index 2013-11-21 23:48:58 UTC (rev 8306)
+++ index 2013-11-22 18:48:56 UTC (rev 8307)
@@ -298,7 +298,7 @@
<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 21 November 2013</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 22 November 2013</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -66791,9 +66791,10 @@
potentially http-origin privacy sensitive -->
<p>Otherwise, if the <a href=#browsing-context>browsing context</a> being navigated is a <a href=#child-browsing-context>child browsing
- context</a> for an <code><a href=#the-iframe-element>iframe</a></code> or <code><a href=#the-object-element>object</a></code> element, then the <a href=#fetch title=fetch>fetching algorithm</a> must be invoked from the <code><a href=#the-iframe-element>iframe</a></code> or
- <code><a href=#the-object-element>object</a></code> element's <a href=#browsing-context-scope-origin>browsing context scope origin</a>, if it has one.</p>
- <!-- potentially http-origin privacy sensitive -->
+ context</a>, then the <a href=#fetch title=fetch>fetching algorithm</a> must be invoked from the
+ <a href=#browsing-context-scope-origin>browsing context scope origin</a> of the <a href=#browsing-context-container>browsing context container</a> of the
+ <a href=#browsing-context>browsing context</a> being navigated, if it has one.</p> <!-- potentially http-origin
+ privacy sensitive -->
</li>
Modified: source
===================================================================
--- source 2013-11-21 23:48:58 UTC (rev 8306)
+++ source 2013-11-22 18:48:56 UTC (rev 8307)
@@ -74398,10 +74398,10 @@
potentially http-origin privacy sensitive -->
<p>Otherwise, if the <span>browsing context</span> being navigated is a <span>child browsing
- context</span> for an <code>iframe</code> or <code>object</code> element, then the <span
- data-x="fetch">fetching algorithm</span> must be invoked from the <code>iframe</code> or
- <code>object</code> element's <span>browsing context scope origin</span>, if it has one.</p>
- <!-- potentially http-origin privacy sensitive -->
+ context</span>, then the <span data-x="fetch">fetching algorithm</span> must be invoked from the
+ <span>browsing context scope origin</span> of the <span>browsing context container</span> of the
+ <span>browsing context</span> being navigated, if it has one.</p> <!-- potentially http-origin
+ privacy sensitive -->
</li>
More information about the Commit-Watchers
mailing list