[html5] r7663 - [e] (0) Make tutorial match actual requirements. Fixing https://www.w3.org/Bugs/ [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-01-28 16:48:49 -0800 (Mon, 28 Jan 2013)
New Revision: 7663

Modified:
   complete.html
   index
   source
Log:
[e] (0) Make tutorial match actual requirements.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=19491
Affected topics: HTML, Workers

Modified: complete.html
===================================================================
--- complete.html	2013-01-28 23:31:04 UTC (rev 7662)
+++ complete.html	2013-01-29 00:48:49 UTC (rev 7663)
@@ -248,7 +248,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 28 January 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 29 January 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -80928,18 +80928,12 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Shared workers are identified in one of two ways: either by the
-  URL of the script used to create it, or by explicit name. When
-  created by name, the URL used by the first page to create the worker
-  with that name is the URL of the script that will be used for that
-  worker. This allows multiple applications on a domain to all use a
-  single shared worker to provide a common service, without the
-  applications having to keep track of a common URL for the script
-  used to provide the service.</p>
+  <p>Shared workers are identified by the URL of the script used to create it, optionally with an
+  explicit name. The name allows multiple instances of a particular shared worker to be started.</p>
 
-  <p class=note>In either case, shared workers are scoped by
-  <a href=#origin>origin</a>. Two different sites using the same names will
-  not collide.</p>
+  <p>Shared workers are scoped by <a href=#origin>origin</a>. Two different sites using the same names will
+  not collide. However, if a page tries to use the same shared worker name as another page on the
+  same site, but with a different script URL, it will fail.</p>
 
   <p>Creating shared workers is done using the <code title=dom-SharedWorker><a href=#dom-sharedworker>SharedWorker()</a></code> constructor. This
   constructor takes the URL to the script to use for its first

Modified: index
===================================================================
--- index	2013-01-28 23:31:04 UTC (rev 7662)
+++ index	2013-01-29 00:48:49 UTC (rev 7663)
@@ -248,7 +248,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 28 January 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 29 January 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -80928,18 +80928,12 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>Shared workers are identified in one of two ways: either by the
-  URL of the script used to create it, or by explicit name. When
-  created by name, the URL used by the first page to create the worker
-  with that name is the URL of the script that will be used for that
-  worker. This allows multiple applications on a domain to all use a
-  single shared worker to provide a common service, without the
-  applications having to keep track of a common URL for the script
-  used to provide the service.</p>
+  <p>Shared workers are identified by the URL of the script used to create it, optionally with an
+  explicit name. The name allows multiple instances of a particular shared worker to be started.</p>
 
-  <p class=note>In either case, shared workers are scoped by
-  <a href=#origin>origin</a>. Two different sites using the same names will
-  not collide.</p>
+  <p>Shared workers are scoped by <a href=#origin>origin</a>. Two different sites using the same names will
+  not collide. However, if a page tries to use the same shared worker name as another page on the
+  same site, but with a different script URL, it will fail.</p>
 
   <p>Creating shared workers is done using the <code title=dom-SharedWorker><a href=#dom-sharedworker>SharedWorker()</a></code> constructor. This
   constructor takes the URL to the script to use for its first

Modified: source
===================================================================
--- source	2013-01-28 23:31:04 UTC (rev 7662)
+++ source	2013-01-29 00:48:49 UTC (rev 7663)
@@ -93857,18 +93857,12 @@
 
   <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
 
-  <p>Shared workers are identified in one of two ways: either by the
-  URL of the script used to create it, or by explicit name. When
-  created by name, the URL used by the first page to create the worker
-  with that name is the URL of the script that will be used for that
-  worker. This allows multiple applications on a domain to all use a
-  single shared worker to provide a common service, without the
-  applications having to keep track of a common URL for the script
-  used to provide the service.</p>
+  <p>Shared workers are identified by the URL of the script used to create it, optionally with an
+  explicit name. The name allows multiple instances of a particular shared worker to be started.</p>
 
-  <p class="note">In either case, shared workers are scoped by
-  <span>origin</span>. Two different sites using the same names will
-  not collide.</p>
+  <p>Shared workers are scoped by <span>origin</span>. Two different sites using the same names will
+  not collide. However, if a page tries to use the same shared worker name as another page on the
+  same site, but with a different script URL, it will fail.</p>
 
   <p>Creating shared workers is done using the <code
   title="dom-SharedWorker">SharedWorker()</code> constructor. This