[html5] r6322 - [giow] (0) Make Facebook work. See http://blogs.msdn.com/b/ieinternals/archive/2 [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-07-23 19:28:08 -0700 (Sat, 23 Jul 2011)
New Revision: 6322

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Make Facebook work. See http://blogs.msdn.com/b/ieinternals/archive/2011/05/17/url-fragments-and-redirects-anchor-hash-missing.aspx

Modified: complete.html
===================================================================
--- complete.html	2011-07-22 14:26:04 UTC (rev 6321)
+++ complete.html	2011-07-24 02:28:08 UTC (rev 6322)
@@ -239,7 +239,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 22 July 2011</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 24 July 2011</h2>
    </hgroup><dl><dt>Multiple-page version:</dt>
     <dd><a href=http://www.whatwg.org/specs/web-apps/current-work/complete/>http://www.whatwg.org/specs/web-apps/current-work/complete/</a></dd>
     <dt>One-page version:</dt>
@@ -64482,8 +64482,17 @@
     origin</a> as the original resource, or the resource is being
     obtained using the POST method or a safe method (in HTTP terms),
     return to <a href=#navigate-fragid-step>the step labeled
-    "fragment identifiers"</a> with the new resource.</p>
+    "fragment identifiers"</a> with the new resource, except that if
+    the <a href=#url>URL</a> of the target of the redirect does not have a
+    fragment identifier and the <a href=#url>URL</a> of the resource that
+    led to the redirect does, then the <a href=#url>URL</a> of the
+    resource that led to the redirect must be propagated to the
+    <a href=#url>URL</a> of the target of the redirect.</p>
 
+    <p class=example>So for instance, if the original URL was "<code title="">http://example.com/#!sample</code>" and "<code title="">http://example.com/</code>" is found to redirect to
+    "<code title="">https://example.com/</code>", the URL of the new
+    resource will be "<code title="">https://example.com/#!sample</code>".</p>
+
     <p>Otherwise, if fetching the resource results in a redirect but
     the <a href=#url>URL</a> of the target of the redirect does not have
     the <a href=#same-origin>same origin</a> as the original resource and the

Modified: index
===================================================================
--- index	2011-07-22 14:26:04 UTC (rev 6321)
+++ index	2011-07-24 02:28:08 UTC (rev 6322)
@@ -243,7 +243,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 22 July 2011</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 24 July 2011</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>
@@ -64354,8 +64354,17 @@
     origin</a> as the original resource, or the resource is being
     obtained using the POST method or a safe method (in HTTP terms),
     return to <a href=#navigate-fragid-step>the step labeled
-    "fragment identifiers"</a> with the new resource.</p>
+    "fragment identifiers"</a> with the new resource, except that if
+    the <a href=#url>URL</a> of the target of the redirect does not have a
+    fragment identifier and the <a href=#url>URL</a> of the resource that
+    led to the redirect does, then the <a href=#url>URL</a> of the
+    resource that led to the redirect must be propagated to the
+    <a href=#url>URL</a> of the target of the redirect.</p>
 
+    <p class=example>So for instance, if the original URL was "<code title="">http://example.com/#!sample</code>" and "<code title="">http://example.com/</code>" is found to redirect to
+    "<code title="">https://example.com/</code>", the URL of the new
+    resource will be "<code title="">https://example.com/#!sample</code>".</p>
+
     <p>Otherwise, if fetching the resource results in a redirect but
     the <a href=#url>URL</a> of the target of the redirect does not have
     the <a href=#same-origin>same origin</a> as the original resource and the

Modified: source
===================================================================
--- source	2011-07-22 14:26:04 UTC (rev 6321)
+++ source	2011-07-24 02:28:08 UTC (rev 6322)
@@ -73285,8 +73285,20 @@
     origin</span> as the original resource, or the resource is being
     obtained using the POST method or a safe method (in HTTP terms),
     return to <a href="#navigate-fragid-step">the step labeled
-    "fragment identifiers"</a> with the new resource.</p>
+    "fragment identifiers"</a> with the new resource, except that if
+    the <span>URL</span> of the target of the redirect does not have a
+    fragment identifier and the <span>URL</span> of the resource that
+    led to the redirect does, then the <span>URL</span> of the
+    resource that led to the redirect must be propagated to the
+    <span>URL</span> of the target of the redirect.</p>
 
+    <p class="example">So for instance, if the original URL was "<code
+    title="">http://example.com/#!sample</code>" and "<code
+    title="">http://example.com/</code>" is found to redirect to
+    "<code title="">https://example.com/</code>", the URL of the new
+    resource will be "<code
+    title="">https://example.com/#!sample</code>".</p>
+
     <p>Otherwise, if fetching the resource results in a redirect but
     the <span>URL</span> of the target of the redirect does not have
     the <span>same origin</span> as the original resource and the