- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 09 Jan 2011 20:41:38 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv8882 Modified Files: Overview.html Log Message: hide some impl things from the author section (whatwg r5753) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.4613 retrieving revision 1.4614 diff -u -d -r1.4613 -r1.4614 --- Overview.html 8 Jan 2011 00:36:21 -0000 1.4613 +++ Overview.html 9 Jan 2011 20:41:33 -0000 1.4614 @@ -2486,11 +2486,15 @@ 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> + plugins.<div class="impl"> + + <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 + <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 class="example">One example of a plugin would be a PDF viewer + a plugin registered for those types, of course) --> + + </div><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 @@ -2501,11 +2505,15 @@ interacting with plugins, as it is expected to be user-agent- and platform-specific. Some UAs might opt to support a plugin mechanism such as the Netscape Plugin API; others might use remote content - converters or have built-in support for certain types. <a href="#refsNPAPI">[NPAPI]</a><p class="warning">Browsers should take extreme care when + converters or have built-in support for certain types. <a href="#refsNPAPI">[NPAPI]</a><div class="impl"> + + <p class="warning">Browsers should take extreme care when interacting with external content intended for <a href="#plugin" title="plugin">plugins</a>. When third-party software is run with the same privileges as the user agent itself, vulnerabilities in the third-party software become as dangerous as those in the user - agent.<h4 id="character-encodings"><span class="secno">2.1.6 </span>Character encodings</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/101">ISSUE-101</a> (us-ascii-ref) blocks progress to Last Call</span><p>The <dfn id="preferred-mime-name">preferred MIME name</dfn> of a character encoding is the + agent.</p> + + </div><h4 id="character-encodings"><span class="secno">2.1.6 </span>Character encodings</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/101">ISSUE-101</a> (us-ascii-ref) blocks progress to Last Call</span><p>The <dfn id="preferred-mime-name">preferred MIME name</dfn> of a character encoding is the name or alias labeled as "preferred MIME name" in the IANA <cite>Character Sets</cite> registry, if there is one, or the encoding's name, if none of the aliases are so labeled. <a href="#refsIANACHARSET">[IANACHARSET]</a><p>An <dfn id="ascii-compatible-character-encoding">ASCII-compatible character encoding</dfn> is a
Received on Sunday, 9 January 2011 20:41:40 UTC