- From: poot <cvsmail@w3.org>
- Date: Wed, 13 Jan 2010 12:30:53 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: Rename text/sandboxed-html to text/html-sandboxed so it sorts
better in lists of MIME types (whatwg r4585)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3660&r2=1.3661&f=h
http://html5.org/tools/web-apps-tracker?from=4584&to=4585
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3660
retrieving revision 1.3661
diff -u -d -r1.3660 -r1.3661
--- Overview.html 13 Jan 2010 03:09:07 -0000 1.3660
+++ Overview.html 13 Jan 2010 03:30:36 -0000 1.3661
@@ -1208,7 +1208,7 @@
<li><a href="#iana"><span class="secno">11 </span>IANA considerations</a>
<ol>
<li><a href="#text-html"><span class="secno">11.1 </span><code>text/html</code></a></li>
- <li><a href="#text-sandboxed-html"><span class="secno">11.2 </span><code>text/sandboxed-html</code></a></li>
+ <li><a href="#text-html-sandboxed"><span class="secno">11.2 </span><code>text/html-sandboxed</code></a></li>
<li><a href="#application-xhtml-xml"><span class="secno">11.3 </span><code>application/xhtml+xml</code></a></li>
<li><a href="#text-cache-manifest"><span class="secno">11.4 </span><code>text/cache-manifest</code></a></li>
<li><a href="#text-ping"><span class="secno">11.5 </span><code>text/ping</code></a></li>
@@ -1631,7 +1631,7 @@
3.7 "Media Types" of RFC 2616, but does not contain any U+003B
SEMICOLON characters (;). In other words, if it consists only of a
type and subtype, with no MIME Type parameters. <a href="#refsHTTP">[HTTP]</a><p>The term <dfn id="html-mime-type">HTML MIME type</dfn> is used to refer to the <a href="#mime-type" title="MIME type">MIME types</a> <code><a href="#text-html">text/html</a></code> and
- <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code>.<h4 id="xml"><span class="secno">2.1.2 </span>XML</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p id="html-namespace">To ease migration from HTML to XHTML, UAs
+ <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code>.<h4 id="xml"><span class="secno">2.1.2 </span>XML</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p id="html-namespace">To ease migration from HTML to XHTML, UAs
conforming to this specification will place elements in HTML in the
<code>http://www.w3.org/1999/xhtml</code> namespace, at least for
the purposes of the DOM and CSS. The term "<dfn id="html-elements">HTML
@@ -17022,7 +17022,7 @@
</div><p class="note">Potentially hostile files can be served from the
same server as the file containing the <code><a href="#the-iframe-element">iframe</a></code> element
- by labeling them as <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code> instead of
+ by labeling them as <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code> instead of
<code><a href="#text-html">text/html</a></code>. This ensures that scripts in the files are
unable to attack the site (as if they were actually served from
another server), even if the user is tricked into visiting those
@@ -38674,7 +38674,7 @@
<code>Document</code> was created</dt>
<dt>If a <code>Document</code> was generated from a resource
- labeled as <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code></dt>
+ labeled as <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code></dt>
<dd>The <a href="#origin">origin</a> is a globally unique identifier
assigned when the <code>Document</code> is created.</dd>
@@ -43989,7 +43989,7 @@
following list, and process the resource as described there:</p>
<dl class="switch"><!-- an <span>HTML MIME type</span> --><dt>"<code><a href="#text-html">text/html</a></code>"</dt>
- <dt>"<code><a href="#text-sandboxed-html">text/sandboxed-html</a></code>"</dt>
+ <dt>"<code><a href="#text-html-sandboxed">text/html-sandboxed</a></code>"</dt>
<dd>Follow the steps given in the <a href="#read-html" title="navigate-html">HTML document</a> section, and abort
these steps.</dd>
@@ -63734,14 +63734,14 @@
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers used with <code><a href="#text-html">text/html</a></code> resources
- refer to <a href="#the-indicated-part-of-the-document">the indicated part of the document</a>.<h3 id="text-sandboxed-html"><span class="secno">11.2 </span><dfn><code>text/sandboxed-html</code></dfn></h3><p>This registration is for community review and will be submitted
+ refer to <a href="#the-indicated-part-of-the-document">the indicated part of the document</a>.<h3 id="text-html-sandboxed"><span class="secno">11.2 </span><dfn><code>text/html-sandboxed</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
- Subject: Registration of media type text/sandboxed-html
+ Subject: Registration of media type text/html-sandboxed
--><dl><dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
- <dd>sandboxed-html</dd>
+ <dd>html-sandboxed</dd>
<dt>Required parameters:</dt>
<dd>No required parameters</dd>
<dt>Optional parameters:</dt>
@@ -63750,17 +63750,17 @@
<dd>Same as for <code><a href="#text-html">text/html</a></code></dd>
<dt>Security considerations:</dt>
<dd>
- <p>The purpose of the <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code> MIME type
+ <p>The purpose of the <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code> MIME type
is to provide a way for content providers to indicate that they
want the file to be interpreted in a manner that does not give the
file's contents access to the rest of the site. This is achieved
by assigning the <code>Document</code> objects generated from
- resources labeled as <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code> unique
+ resources labeled as <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code> unique
origins.</p>
<p>To avoid having legacy user agents treating resources labeled
- as <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code> as regular
+ as <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code> as regular
<code><a href="#text-html">text/html</a></code> files, authors should avoid using the <code title="">.html</code> or <code title="">.htm</code> extensions for
- resources labeled as <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code>.</p>
+ resources labeled as <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code>.</p>
<p>Beyond this, the type is identical to <code><a href="#text-html">text/html</a></code>,
and the same considerations apply.</p>
</dd>
@@ -63769,7 +63769,7 @@
<dt>Published specification:</dt>
<dd>
This document is the relevant specification. Labeling a resource
- with the <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code> type asserts that the
+ with the <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code> type asserts that the
resource is an <a href="#html-documents" title="HTML documents">HTML document</a>
using <a href="#syntax">the HTML syntax</a>.
</dd>
@@ -63778,7 +63778,7 @@
<dt>Additional information:</dt>
<dd>
<dl><dt>Magic number(s):</dt>
- <dd>Documents labeled as <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code> are
+ <dd>Documents labeled as <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code> are
heuristically indistinguishable from those labeled as
<code><a href="#text-html">text/html</a></code>.</dd>
<dt>File extension(s):</dt>
@@ -63796,7 +63796,7 @@
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
- </dl><p>Fragment identifiers used with <code><a href="#text-sandboxed-html">text/sandboxed-html</a></code>
+ </dl><p>Fragment identifiers used with <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code>
resources refer to <a href="#the-indicated-part-of-the-document">the indicated part of the
document</a>.<h3 id="application-xhtml-xml"><span class="secno">11.3 </span><dfn><code>application/xhtml+xml</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
Received on Wednesday, 13 January 2010 03:31:22 UTC