[html5] r3390 - [e] (0) Make the definition of 'plugin' actually comprehensible.
whatwg at whatwg.org
whatwg at whatwg.org
Sun Jul 12 22:20:20 PDT 2009
Author: ianh
Date: 2009-07-12 22:20:18 -0700 (Sun, 12 Jul 2009)
New Revision: 3390
Modified:
index
source
Log:
[e] (0) Make the definition of 'plugin' actually comprehensible.
Modified: index
===================================================================
--- index 2009-07-13 05:12:49 UTC (rev 3389)
+++ index 2009-07-13 05:20:18 UTC (rev 3390)
@@ -1646,12 +1646,14 @@
<h4 id=plugins><span class=secno>2.1.4 </span>Plugins</h4>
- <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content handler,
- typically a third-party content handler, for Web content types that
- are not supported by the user agent natively, or for content types
- that do not expose a DOM, that supports rendering the content as
- part of the user agent's interface.</p>
+ <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content handler
+ for Web content types that are either not supported by the user
+ agent natively or that do not expose a DOM, which supports rendering
+ the content as part of the user agent's interface.</p>
+ <p>Typically such content handlers are provided by third
+ parties.</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 2009-07-13 05:12:49 UTC (rev 3389)
+++ source 2009-07-13 05:20:18 UTC (rev 3390)
@@ -666,12 +666,14 @@
<h4>Plugins</h4>
- <p>The term <dfn>plugin</dfn> is used to mean any content handler,
- typically a third-party content handler, for Web content types that
- are not supported by the user agent natively, or for content types
- that do not expose a DOM, that supports rendering the content as
- part of the user agent's interface.</p>
+ <p>The term <dfn>plugin</dfn> is used to mean any content handler
+ for Web content types that are either not supported by the user
+ agent natively or that do not expose a DOM, which supports rendering
+ the content as part of the user agent's interface.</p>
+ <p>Typically such content handlers are provided by third
+ parties.</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
More information about the Commit-Watchers
mailing list