hixie: Make Facebook work. See http://blogs.msdn.com/b/ieinternals/archive/2011/05/17/url-fragments-and-redirects-anchor-hash-missing.aspx (whatwg r6322)

hixie: Make Facebook work. See
http://blogs.msdn.com/b/ieinternals/archive/2011/05/17/url-fragments-
and-redirects-anchor-hash-missing.aspx (whatwg r6322)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5052&r2=1.5053&f=h
http://html5.org/tools/web-apps-tracker?from=6321&to=6322

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5052
retrieving revision 1.5053
diff -u -d -r1.5052 -r1.5053
--- Overview.html 22 Jul 2011 14:26:11 -0000 1.5052
+++ Overview.html 24 Jul 2011 02:28:17 -0000 1.5053
@@ -318,7 +318,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-22-july-2011">Editor's Draft 22 July 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-24-july-2011">Editor's Draft 24 July 2011</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -464,7 +464,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 22 July 2011 Editor's Draft.
+  This specification is the 24 July 2011 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
   actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
   group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -45965,7 +45965,16 @@
     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

Received on Sunday, 24 July 2011 02:28:47 UTC