[e] (0) add some worker demo links

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9387

git-svn-id: http://svn.whatwg.org/webapps@4998 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -57297,6 +57297,9 @@ <h4 id=introduction-3><span class=secno>6.6.1 </span>Introduction</h4>
   application cache before the user agent has updated it, and even
   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>6.6.1.1 </span>Event summary</h5>
 
@@ -65734,6 +65737,8 @@ <h5 id=shared-workers-introduction><span class=secno>9.1.2.4 </span>Shared worke
 }
 </pre>
 
+  <p><a href=http://www.whatwg.org/demos/workers/shared/001.html>View this example online</a>.</p>
+
   <hr><p>This second example extends the first one by changing two things:
   first, messages are received using <code title="">addEventListener()</code> instead of an <a href=#event-handler-idl-attributes title="event
   handler IDL attributes">event handler IDL attribute</a>, and
@@ -65769,6 +65774,8 @@ <h5 id=shared-workers-introduction><span class=secno>9.1.2.4 </span>Shared worke
 }
 </pre>
 
+  <p><a href=http://www.whatwg.org/demos/workers/shared/002.html>View this example online</a>.</p>
+
   <hr><p>Finally, the example is extended to show how two pages can
   connect to the same worker; in this case, the second page is merely
   in an <code><a href=#the-iframe-element>iframe</a></code> on the first page, but the same principle
@@ -65819,6 +65826,8 @@ <h5 id=shared-workers-introduction><span class=secno>9.1.2.4 </span>Shared worke
 }
 </pre>
 
+  <p><a href=http://www.whatwg.org/demos/workers/shared/003.html>View this example online</a>.</p>
+
 
   <h5 id=shared-state-using-a-shared-worker><span class=secno>9.1.2.5 </span>Shared state using a shared worker</h5>
 

index

@@ -57201,6 +57201,9 @@ clock.js</pre>
   application cache before the user agent has updated it, and even
   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>6.6.1.1 </span>Event summary</h5>
 

source

@@ -64472,6 +64472,9 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
   application cache before the user agent has updated it, and even
   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">Event summary</h5>
 
@@ -74212,6 +74215,8 @@ v2 (well, really v0):
 
   <pre>EXAMPLE workers/shared/001/test.js</pre>
 
+  <p><a href="http://www.whatwg.org/demos/workers/shared/001.html">View this example online</a>.</p>
+
   <hr>
 
   <p>This second example extends the first one by changing two things:
@@ -74230,6 +74235,8 @@ v2 (well, really v0):
 
   <pre>EXAMPLE workers/shared/002/test.js</pre>
 
+  <p><a href="http://www.whatwg.org/demos/workers/shared/002.html">View this example online</a>.</p>
+
   <hr>
 
   <p>Finally, the example is extended to show how two pages can
@@ -74250,6 +74257,8 @@ v2 (well, really v0):
 
   <pre>EXAMPLE workers/shared/003/test.js</pre>
 
+  <p><a href="http://www.whatwg.org/demos/workers/shared/003.html">View this example online</a>.</p>
+
 
   <h5>Shared state using a shared worker</h5>