hixie: add some worker demo links (whatwg r4998)

hixie: add some worker demo links (whatwg r4998)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4015&r2=1.4016&f=h
http://html5.org/tools/web-apps-tracker?from=4997&to=4998

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4015
retrieving revision 1.4016
diff -u -d -r1.4015 -r1.4016
--- Overview.html 12 Apr 2010 07:57:49 -0000 1.4015
+++ Overview.html 12 Apr 2010 08:04:12 -0000 1.4016
@@ -44094,7 +44094,9 @@
   served over TLS (encrypted, using <code title="">https:</code>) are
   overridden by manifests. Thus, pages will not expire from an
   application cache before the user agent has updated it, and even
-  applications served over TLS can be made to work offline.<h5 id="appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</h5><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>When the user visits a page that declares a manifest, the browser
+  applications served over TLS can be made to work offline.</p><!--(doesn't currently function)
+  <p><a href="http://www.whatwg.org/demos/offline/clock/clock2.html">View this example online</a>.</p>
+--><h5 id="appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</h5><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>When the user visits a page that declares a manifest, the browser
   will try to update the cache. It does this by fetching a copy of the
   manifest and, if the manifest has changed since the user agent last
   saw it, redownloading all the resources it mentions and caching them

Received on Monday, 12 April 2010 08:04:53 UTC