- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 14 Feb 2010 09:36:24 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv22645 Modified Files: Overview.html Log Message: Try to define 'plugin' better. (whatwg r4725) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3772 retrieving revision 1.3773 diff -u -d -r1.3772 -r1.3773 --- Overview.html 14 Feb 2010 09:26:05 -0000 1.3772 +++ Overview.html 14 Feb 2010 09:36:20 -0000 1.3773 @@ -1721,10 +1721,13 @@ 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 - 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>Typically such content handlers are provided by third - parties.<p class="example">One example of a plugin would be a PDF viewer + that supports displaying content as part of the user agent's + rendering of a <code>Document</code> object, but that neither acts + as a <a href="#child-browsing-context">child browsing context</a> of the + <code>Document</code> nor introduces any <code>Node</code> objects + to the <code>Document</code>'s DOM.<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 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 Sunday, 14 February 2010 09:36:26 UTC