[html5] r4996 - [e] (0) Try to clarify the meaning of 'plugin' once more. Fixing http://www.w3.o [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-04-12 00:51:18 -0700 (Mon, 12 Apr 2010)
New Revision: 4996

Modified:
   complete.html
   index
   source
Log:
[e] (0) Try to clarify the meaning of 'plugin' once more.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9221

Modified: complete.html
===================================================================
--- complete.html	2010-04-12 07:27:11 UTC (rev 4995)
+++ complete.html	2010-04-12 07:51:18 UTC (rev 4996)
@@ -2750,23 +2750,23 @@
 
   <h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
 
-  <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content handler
-  that supports displaying content as part of the user agent's
-  rendering of a <code><a href=#document>Document</a></code> object, but that neither acts
-  as a <a href=#child-browsing-context>child browsing context</a> of the
-  <code><a href=#document>Document</a></code> nor introduces any <code><a href=#node>Node</a></code> objects
-  to the <code><a href=#document>Document</a></code>'s DOM.</p>
+  <p>The term <dfn id=plugin>plugin</dfn> refers to a user-agent defined set of
+  content handlers used by the user agent that can take part in the
+  user agent's rendering of a <code><a href=#document>Document</a></code> object, but that
+  neither act as <a href=#child-browsing-context title="child browsing context">child browsing
+  contexts</a> of the <code><a href=#document>Document</a></code> nor introduce any
+  <code><a href=#node>Node</a></code> objects to the <code><a href=#document>Document</a></code>'s DOM.</p>
 
+  <p>Typically such content handlers are provided by third parties,
+  though a user agent can also designate built-in content handlers as
+  plugins.</p>
+
   <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) -->
 
-  <p>Typically such content handlers are provided by third parties,
-  though a user agent can designate content handlers to be
-  plugins.</p>
-
   <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

Modified: index
===================================================================
--- index	2010-04-12 07:27:11 UTC (rev 4995)
+++ index	2010-04-12 07:51:18 UTC (rev 4996)
@@ -2648,23 +2648,23 @@
 
   <h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
 
-  <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content handler
-  that supports displaying content as part of the user agent's
-  rendering of a <code><a href=#document>Document</a></code> object, but that neither acts
-  as a <a href=#child-browsing-context>child browsing context</a> of the
-  <code><a href=#document>Document</a></code> nor introduces any <code><a href=#node>Node</a></code> objects
-  to the <code><a href=#document>Document</a></code>'s DOM.</p>
+  <p>The term <dfn id=plugin>plugin</dfn> refers to a user-agent defined set of
+  content handlers used by the user agent that can take part in the
+  user agent's rendering of a <code><a href=#document>Document</a></code> object, but that
+  neither act as <a href=#child-browsing-context title="child browsing context">child browsing
+  contexts</a> of the <code><a href=#document>Document</a></code> nor introduce any
+  <code><a href=#node>Node</a></code> objects to the <code><a href=#document>Document</a></code>'s DOM.</p>
 
+  <p>Typically such content handlers are provided by third parties,
+  though a user agent can also designate built-in content handlers as
+  plugins.</p>
+
   <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) -->
 
-  <p>Typically such content handlers are provided by third parties,
-  though a user agent can designate content handlers to be
-  plugins.</p>
-
   <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

Modified: source
===================================================================
--- source	2010-04-12 07:27:11 UTC (rev 4995)
+++ source	2010-04-12 07:51:18 UTC (rev 4996)
@@ -1614,23 +1614,23 @@
 
   <h4>Plugins</h4>
 
-  <p>The term <dfn>plugin</dfn> is used to mean any content handler
-  that supports displaying content as part of the user agent's
-  rendering of a <code>Document</code> object, but that neither acts
-  as a <span>child browsing context</span> of the
-  <code>Document</code> nor introduces any <code>Node</code> objects
-  to the <code>Document</code>'s DOM.</p>
+  <p>The term <dfn>plugin</dfn> refers to a user-agent defined set of
+  content handlers used by the user agent that can take part in the
+  user agent's rendering of a <code>Document</code> object, but that
+  neither act as <span title="child browsing context">child browsing
+  contexts</span> of the <code>Document</code> nor introduce any
+  <code>Node</code> objects to the <code>Document</code>'s DOM.</p>
 
+  <p>Typically such content handlers are provided by third parties,
+  though a user agent can also designate built-in content handlers as
+  plugins.</p>
+
   <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) -->
 
-  <p>Typically such content handlers are provided by third parties,
-  though a user agent can designate content handlers to be
-  plugins.</p>
-
   <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