W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2008

html5/spec Overview.html,1.1102,1.1103

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 23 Jul 2008 21:49:53 +0000
To: public-html-commits@w3.org
Message-Id: <E1KLmDZ-0003fD-Rt@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv13858

Modified Files:
Log Message:
Spec out the behaviour we see in IE for navigating to about:blank or javascript: URLs vs other URLs. (whatwg r1913)

Index: Overview.html
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1102
retrieving revision 1.1103
diff -u -d -r1.1102 -r1.1103
--- Overview.html	23 Jul 2008 21:08:41 -0000	1.1102
+++ Overview.html	23 Jul 2008 21:49:50 -0000	1.1103
@@ -35043,6 +35043,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
Received on Wednesday, 23 July 2008 21:59:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:09:17 UTC