W3C home > Mailing lists > Public > public-html-diffs@w3.org > January 2010

hixie: Navigation should be async. This wasn't properly described before. (whatwg r4495)

From: poot <cvsmail@w3.org>
Date: Wed, 6 Jan 2010 12:33:46 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100106033346.7862E2BC6F@toro.w3.mag.keio.ac.jp>
hixie: Navigation should be async. This wasn't properly described
before. (whatwg r4495)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3594&r2=1.3595&f=h
http://html5.org/tools/web-apps-tracker?from=4494&to=4495

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3594
retrieving revision 1.3595
diff -u -d -r1.3594 -r1.3595
--- Overview.html	6 Jan 2010 03:31:04 -0000	1.3594
+++ Overview.html	6 Jan 2010 03:33:35 -0000	1.3595
@@ -47420,8 +47420,9 @@
     <code><a href="#about:blank">about:blank</a></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 <a href="#concept-script" title="concept-script">script</a> invoked the navigation steps,
-    if they were invoked by script.</p>
+    this point the user agents must return to whatever algorithm
+    invoked the navigation steps and must continue these steps
+    asynchronously.</p>
 
    </li>
Received on Wednesday, 6 January 2010 03:34:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:45 UTC