W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2010

html5/spec-author-view Overview.html,1.855,1.856 infrastructure.html,1.588,1.589 spec.html,1.863,1.864

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 12 Apr 2010 07:57:24 +0000
To: public-html-commits@w3.org
Message-Id: <E1O1EWK-0006xe-2n@lionel-hutz.w3.org>
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv26647

Modified Files:
	Overview.html infrastructure.html spec.html 
Log Message:
Try to clarify the meaning of 'plugin' once more. (whatwg r4996)

[updated by splitter]


Index: infrastructure.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/infrastructure.html,v
retrieving revision 1.588
retrieving revision 1.589
diff -u -d -r1.588 -r1.589
--- infrastructure.html	8 Apr 2010 23:57:35 -0000	1.588
+++ infrastructure.html	12 Apr 2010 07:57:21 -0000	1.589
@@ -410,18 +410,18 @@
   data.</p><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="references.html#refsDOMEVENTS">[DOMEVENTS]</a></p><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><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="browsers.html#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>A user agent must not consider the types <code>text/plain</code>
+  http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href="references.html#refsDOMEVENTS">[DOMEVENTS]</a></p><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><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="browsers.html#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
+  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="browsers.html#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

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.855
retrieving revision 1.856
diff -u -d -r1.855 -r1.856
--- Overview.html	12 Apr 2010 07:38:04 -0000	1.855
+++ Overview.html	12 Apr 2010 07:57:21 -0000	1.856
@@ -305,7 +305,7 @@
    </dl><p>This specification is available in the following formats: 
     <a href="spec.html">single page HTML</a>,
     <a href="Overview.html">multipage HTML</a>.
-This is revision 1.4013.
+This is revision 1.4014.
    </p> 
    <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.863
retrieving revision 1.864
diff -u -d -r1.863 -r1.864
--- spec.html	12 Apr 2010 07:38:04 -0000	1.863
+++ spec.html	12 Apr 2010 07:57:21 -0000	1.864
@@ -303,7 +303,7 @@
    </dl><p>This specification is available in the following formats: 
     <a href=spec.html>single page HTML</a>,
     <a href=Overview.html>multipage HTML</a>.
-This is revision 1.4013.
+This is revision 1.4014.
    </p> 
    <p class=copyright><a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a>
    © 2010 <a href=http://www.w3.org/><abbr title="World Wide
@@ -1959,18 +1959,18 @@
   data.</p><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></p><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><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>A user agent must not consider the types <code>text/plain</code>
+  http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p><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><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
+  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:57:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 12 April 2010 07:57:26 GMT