[html5] r1913 - [] (0) Spec out the behaviour we see in IE for navigating to about:blank or java [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2008-07-23 14:49:16 -0700 (Wed, 23 Jul 2008)
New Revision: 1913

Modified:
   index
   source
Log:
[] (0) Spec out the behaviour we see in IE for navigating to about:blank or javascript: URLs vs other URLs.

Modified: index
===================================================================
--- index	2008-07-23 21:08:07 UTC (rev 1912)
+++ index	2008-07-23 21:49:16 UTC (rev 1913)
@@ -34972,6 +34972,15 @@
      return to <a href="#navigate-fragid-step">the step labeled "fragment
      identifiers"</a> with the new resource.</p>
 
+    <p>If fetching the resource is instantaneous, as it should be for <a
+     href="#the-javascript" title="javascript protocol"><code
+     title="">javascript:</code> URLs</a> and <code>about:blank</code>, then
+     this must be synchronous, but if fetching the resource depends on
+     external resources, as it usually does for URLs that use HTTP or other
+     networking protocols, then at this point the user agents must yield to
+     whatever script invoked the navigation steps, if they were invoked by
+     script.</p>
+
     <p class=example>For example, imagine an HTML page with an associated
      application cache displaying an image and a form, where the image is
      also used by several other application caches. If the user right-clicks

Modified: source
===================================================================
--- source	2008-07-23 21:08:07 UTC (rev 1912)
+++ source	2008-07-23 21:49:16 UTC (rev 1913)
@@ -32448,6 +32448,15 @@
     redirect, return to <a href="#navigate-fragid-step">the step
     labeled "fragment identifiers"</a> with the new resource.</p>
 
+    <p>If fetching the resource is instantaneous, as it should be for
+    <span title="javascript protocol"><code
+    title="">javascript:</code> URLs</span> and
+    <code>about:blank</code>, then this must be synchronous, but if
+    fetching the resource depends on external resources, as it usually
+    does for URLs that use HTTP or other networking protocols, then at
+    this point the user agents must yield to whatever script invoked
+    the navigation steps, if they were invoked by script.</p>
+
     <p class="example">For example, imagine an HTML page with an
     associated application cache displaying an image and a form, where
     the image is also used by several other application caches. If the