hixie: Try to clarify the meaning of 'plugin' once more. (whatwg r4996)

hixie: Try to clarify the meaning of 'plugin' once more. (whatwg r4996)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4013&r2=1.4014&f=h
http://html5.org/tools/web-apps-tracker?from=4995&to=4996

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4013
retrieving revision 1.4014
diff -u -d -r1.4013 -r1.4014
--- Overview.html 12 Apr 2010 07:27:15 -0000 1.4013
+++ Overview.html 12 Apr 2010 07:51:23 -0000 1.4014
@@ -2293,18 +2293,18 @@
   data.<p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used interchangeably in the context of
   events, as in the DOM Events specifications. The term <dfn id="concept-events-trusted" title="concept-events-trusted">trusted event</dfn> is used as
   defined by the DOM Events specification. <!--
-  http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href="#refsDOMEVENTS">[DOMEVENTS]</a><h4 id="plugins"><span class="secno">2.1.5 </span>Plugins</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><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>A user agent must not consider the types <code>text/plain</code>
+  http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href="#refsDOMEVENTS">[DOMEVENTS]</a><h4 id="plugins"><span class="secno">2.1.5 </span>Plugins</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><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>Typically such content handlers are provided by third parties,
+  though a user agent can also designate built-in content handlers as
+  plugins.<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 class="example">One example of a plugin would be a PDF viewer
+  a plugin registered for those types, of course) --><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
   regardless of whether the party that implemented the PDF viewer

Received on Monday, 12 April 2010 07:52:07 UTC