[html5] r5753 - [e] (0) hide some impl things from the author section

[whatwg at whatwg.org]

Author: ianh
Date: 2011-01-09 12:41:28 -0800 (Sun, 09 Jan 2011)
New Revision: 5753

Modified:
   complete.html
   index
   source
Log:
[e] (0) hide some impl things from the author section

Modified: complete.html
===================================================================
--- complete.html	2011-01-08 00:32:46 UTC (rev 5752)
+++ complete.html	2011-01-09 20:41:28 UTC (rev 5753)
@@ -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 — 8 January 2011</h2>
+    <h2 class="no-num no-toc">Living Standard — 9 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>-->
@@ -2819,12 +2819,16 @@
   though a user agent can also designate built-in content handlers as
   plugins.</p>
 
+  <div class=impl>
+
   <p>A user agent must not consider the types <code>text/plain</code>
   and <code>application/octet-stream</code> as having a registered
   <a href=#plugin>plugin</a>.</p> <!-- because of the way <object> handles
   those types, if nothing else (it also doesn't make any sense to have
   a plugin registered for those types, of course) -->
 
+  </div>
+
   <p class=example>One example of a plugin would be a PDF viewer
   that is instantiated in a <a href=#browsing-context>browsing context</a> when the
   user navigates to a PDF file. This would count as a plugin
@@ -2840,13 +2844,17 @@
   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>
 
+  <div class=impl>
+
   <p class=warning>Browsers should take extreme care when
   interacting with external content intended for <a href=#plugin title=plugin>plugins</a>. When third-party software is run with
   the same privileges as the user agent itself, vulnerabilities in the
   third-party software become as dangerous as those in the user
   agent.</p>
 
+  </div>
 
+
   <h4 id=character-encodings><span class=secno>2.1.6 </span>Character encodings</h4>
 
   <p>The <dfn id=preferred-mime-name>preferred MIME name</dfn> of a character encoding is the

Modified: index
===================================================================
--- index	2011-01-08 00:32:46 UTC (rev 5752)
+++ index	2011-01-09 20:41:28 UTC (rev 5753)
@@ -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 — 8 January 2011</h2>
+    <h2 class="no-num no-toc">Living Standard — 9 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>-->
@@ -2798,12 +2798,16 @@
   though a user agent can also designate built-in content handlers as
   plugins.</p>
 
+  <div class=impl>
+
   <p>A user agent must not consider the types <code>text/plain</code>
   and <code>application/octet-stream</code> as having a registered
   <a href=#plugin>plugin</a>.</p> <!-- because of the way <object> handles
   those types, if nothing else (it also doesn't make any sense to have
   a plugin registered for those types, of course) -->
 
+  </div>
+
   <p class=example>One example of a plugin would be a PDF viewer
   that is instantiated in a <a href=#browsing-context>browsing context</a> when the
   user navigates to a PDF file. This would count as a plugin
@@ -2819,13 +2823,17 @@
   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>
 
+  <div class=impl>
+
   <p class=warning>Browsers should take extreme care when
   interacting with external content intended for <a href=#plugin title=plugin>plugins</a>. When third-party software is run with
   the same privileges as the user agent itself, vulnerabilities in the
   third-party software become as dangerous as those in the user
   agent.</p>
 
+  </div>
 
+
   <h4 id=character-encodings><span class=secno>2.1.6 </span>Character encodings</h4>
 
   <p>The <dfn id=preferred-mime-name>preferred MIME name</dfn> of a character encoding is the

Modified: source
===================================================================
--- source	2011-01-08 00:32:46 UTC (rev 5752)
+++ source	2011-01-09 20:41:28 UTC (rev 5753)
@@ -1719,12 +1719,16 @@
   though a user agent can also designate built-in content handlers as
   plugins.</p>
 
+  <div class="impl">
+
   <p>A user agent must not consider the types <code>text/plain</code>
   and <code>application/octet-stream</code> as having a registered
   <span>plugin</span>.</p> <!-- because of the way <object> handles
   those types, if nothing else (it also doesn't make any sense to have
   a plugin registered for those types, of course) -->
 
+  </div>
+
   <p class="example">One example of a plugin would be a PDF viewer
   that is instantiated in a <span>browsing context</span> when the
   user navigates to a PDF file. This would count as a plugin
@@ -1741,6 +1745,8 @@
   converters or have built-in support for certain types. <a
   href="#refsNPAPI">[NPAPI]</a></p>
 
+  <div class="impl">
+
   <p class="warning">Browsers should take extreme care when
   interacting with external content intended for <span
   title="plugin">plugins</span>. When third-party software is run with
@@ -1748,7 +1754,9 @@
   third-party software become as dangerous as those in the user
   agent.</p>
 
+  </div>
 
+
   <h4>Character encodings</h4>
 
   <p>The <dfn>preferred MIME name</dfn> of a character encoding is the