[e] (0) clarify this note's implications.

git-svn-id: http://svn.whatwg.org/webapps@5787 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jan 18, 2011 · 1904c2e · 1904c2e
1 parent 6d7213a
commit 1904c2e
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 6 deletions.
diff --git a/complete.html b/complete.html
@@ -221,7 +221,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; 14 January 2011</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; 18 January 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -2849,7 +2849,9 @@ <h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
   interacting with plugins, as it is expected to be user-agent- and
   platform-specific. Some UAs might opt to support a plugin mechanism
   such as the Netscape Plugin API; others might use remote content
-  converters or have built-in support for certain types. <a href=#refsNPAPI>[NPAPI]</a></p>
+  converters or have built-in support for certain types. Indeed, this
+  specification doesn't require user agents to support plugins at all.
+  <a href=#refsNPAPI>[NPAPI]</a></p>
 
   <div class=impl>
 

diff --git a/index b/index
@@ -225,7 +225,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; 14 January 2011</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; 18 January 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -2828,7 +2828,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   interacting with plugins, as it is expected to be user-agent- and
   platform-specific. Some UAs might opt to support a plugin mechanism
   such as the Netscape Plugin API; others might use remote content
-  converters or have built-in support for certain types. <a href=#refsNPAPI>[NPAPI]</a></p>
+  converters or have built-in support for certain types. Indeed, this
+  specification doesn't require user agents to support plugins at all.
+  <a href=#refsNPAPI>[NPAPI]</a></p>
 
   <div class=impl>
 

diff --git a/source b/source
@@ -1746,8 +1746,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   interacting with plugins, as it is expected to be user-agent- and
   platform-specific. Some UAs might opt to support a plugin mechanism
   such as the Netscape Plugin API; others might use remote content
-  converters or have built-in support for certain types. <a
-  href="#refsNPAPI">[NPAPI]</a></p>
+  converters or have built-in support for certain types. Indeed, this
+  specification doesn't require user agents to support plugins at all.
+  <a href="#refsNPAPI">[NPAPI]</a></p>
 
   <div class="impl">