Skip to content

Commit

Permalink
[] (0) A variety of mostly editorial fixes: XML MIME type xref; resol…
Browse files Browse the repository at this point in the history 
…ve some minor issues for plugins, collect references.

git-svn-id: http://svn.whatwg.org/webapps@3284 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Jun 16, 2009
1 parent b6c521b commit 9e8c47b
Show file tree
Hide file tree
Showing 2 changed files with 58 additions and 51 deletions.
54 changes: 28 additions & 26 deletions index
View file
Expand Up @@ -1336,13 +1336,13 @@
document by Web browsers.</p>

<p>The second concrete syntax uses XML, and is known as
"XHTML5". When a document is transmitted with an XML MIME type, such
as <code title="">application/xhtml+xml</code>, then it is processed
by an XML processor by Web browsers, and treated as an "XHTML5"
document. Authors are reminded that the processing for XML and HTML
differs; in particular, even minor syntax errors will prevent an XML
document from being rendered fully, whereas they would be ignored in
the "HTML5" syntax.</p>
"XHTML5". When a document is transmitted with an <a href=#xml-mime-type>XML MIME
type</a>, such as <code title="">application/xhtml+xml</code>,
then it is processed by an XML processor by Web browsers, and
treated as an "XHTML5" document. Authors are reminded that the
processing for XML and HTML differs; in particular, even minor
syntax errors will prevent an XML document from being rendered
fully, whereas they would be ignored in the "HTML5" syntax.</p>

<p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
represent the same content. For example, namespaces cannot be
Expand Down Expand Up @@ -1537,6 +1537,10 @@
not an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string
"<code title="">xml</code>". <a href=#refsXML>[XML]</a></p>

<p>The term <dfn id=xml-mime-type>XML MIME type</dfn> is used to refer to the MIME
types <code title="">text/xml</code>, <code title="">application/xml</code>, and any MIME type ending with the
four characters "<code title="">+xml</code>". <a href=#refsRFC3023>[RFC3023]</a></p>


<h4 id=dom-trees><span class=secno>2.1.2 </span>DOM trees</h4>

Expand Down Expand Up @@ -1924,8 +1928,8 @@

<p id=authors-using-xhtml>XML documents that use elements or
attributes from the <a href=#html-namespace-0>HTML namespace</a> and that are served
over the wire (e.g. by HTTP) must be sent using an XML MIME type
such as <code>application/xml</code> or
over the wire (e.g. by HTTP) must be sent using an <a href=#xml-mime-type>XML MIME
type</a> such as <code>application/xml</code> or
<code>application/xhtml+xml</code> and must not be served as
<code>text/html</code>. <a href=#refsRFC3023>[RFC3023]</a></p>

Expand Down Expand Up @@ -4857,8 +4861,6 @@

<h4 id=content-type-sniffing><span class=secno>2.6.3 </span>Determining the type of a resource</h4>

<!-- MIMESNIFF = http://tools.ietf.org/html/draft-abarth-mime-sniff -->

<p>The <dfn id=content-type title=Content-Type>Content-Type metadata</dfn> of a
resource must be obtained and interpreted in a manner consistent
with the requirements of the Content-Type Processing Model
Expand Down Expand Up @@ -18264,7 +18266,8 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
<h4 id=the-embed-element><span class=secno>4.8.4 </span>The <dfn><code>embed</code></dfn> element</h4>

<!--
XXX we have all kinds of quirks we should define, as e.g. shown in:
we have all kinds of quirks we should define if they come up during
testing, as e.g. shown in:
http://mxr.mozilla.org/mozilla-central/source/layout/generic/nsObjectFrame.cpp
http://trac.webkit.org/browser/trunk/WebCore/html/HTMLEmbedElement.cpp
http://trac.webkit.org/browser/trunk/WebCore/rendering/RenderPartObject.cpp (updateWidget)
Expand Down Expand Up @@ -18394,19 +18397,16 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
<li>

<p>Otherwise, if the <a href=#url-path title=url-path>&lt;path&gt;</a>
component of the <a href=#url>URL</a> of the specified resource <!--
XXX before or after redirects? --> matches a pattern that a
<a href=#plugin>plugin</a> supports, then the <span>content's type</span>
is the type that that plugin can handle.</p>
component of the <a href=#url>URL</a> of the specified resource (after
any redirects) matches a pattern that a <a href=#plugin>plugin</a>
supports, then the <span>content's type</span> is the type that
that plugin can handle.</p>

<p class=example>For example, a plugin might say that it can
handle resources with <a href=#url-path title=url-path>&lt;path&gt;</a>
components that end with the four character string "<code title="">.swf</code>".</p>

<p class=XXX>It would be better if browsers didn't do
extension sniffing like this, and only based their decision on the
actual contents of the resource. Couldn't we just apply the
<span>sniffed type of a resource</span> steps?</p>
<!-- it's sad that we have to do extension sniffing. sigh. -->

</li>

Expand Down Expand Up @@ -18694,8 +18694,8 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
</dd>


<dt>If the <var title="">resource type</var> is an <span>XML MIME
type</span><!-- XXX xref --></dt>
<dt>If the <var title="">resource type</var> is an <a href=#xml-mime-type>XML MIME
type</a></dt>
<dt>If the <var title="">resource type</var> is HTML</dt>
<dt>If the <var title="">resource type</var> does not start with
"<code>image/</code>"</dt>
Expand Down Expand Up @@ -51067,6 +51067,7 @@ style/default.css</pre>
<dd>Follow the steps given in the <a href=#read-html title=navigate-html>HTML document</a> section, and abort
these steps.</dd>

<!-- an <span>XML MIME type</span> -->
<dt>Any type ending in "+xml"</dt>
<dt>"application/xml"</dt>
<dt>"text/xml"</dt>
Expand Down Expand Up @@ -51467,12 +51468,12 @@ style/default.css</pre>
attention. If there is no indicated part, then the user agent must
not scroll anywhere.</p>

<p><dfn id=the-indicated-part-of-the-document>The indicated part of the document</dfn> is the one that
the fragment identifier, if any, identifies. The semantics of the
<p><dfn id=the-indicated-part-of-the-document>The indicated part of the document</dfn> is the one that the
fragment identifier, if any, identifies. The semantics of the
fragment identifier in terms of mapping it to a specific DOM Node is
defined by the MIME type specification of the document's MIME Type
(for example, the processing of fragment identifiers for XML MIME
types is the responsibility of RFC3023).</p>
(for example, the processing of fragment identifiers for <a href=#xml-mime-type title="XML MIME type">XML MIME types</a> is the responsibility of
RFC3023).</p>

<p>For HTML documents (and the <code>text/html</code> MIME type),
the following processing model must be followed to determine what
Expand Down Expand Up @@ -70076,6 +70077,7 @@ time:empty { binding: <i title="">time</i>; }</pre>

[IANACHARSET] http://www.iana.org/assignments/character-sets
[ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
[MIMESNIFF] http://tools.ietf.org/html/draft-abarth-mime-sniff
[RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
[SCSU] http://www.unicode.org/unicode/reports/tr6/
[SHIFTJIS] JIS X0208:1997
Expand Down
55 changes: 30 additions & 25 deletions source
View file
Expand Up @@ -283,13 +283,13 @@
document by Web browsers.</p>

<p>The second concrete syntax uses XML, and is known as
"XHTML5". When a document is transmitted with an XML MIME type, such
as <code title="">application/xhtml+xml</code>, then it is processed
by an XML processor by Web browsers, and treated as an "XHTML5"
document. Authors are reminded that the processing for XML and HTML
differs; in particular, even minor syntax errors will prevent an XML
document from being rendered fully, whereas they would be ignored in
the "HTML5" syntax.</p>
"XHTML5". When a document is transmitted with an <span>XML MIME
type</span>, such as <code title="">application/xhtml+xml</code>,
then it is processed by an XML processor by Web browsers, and
treated as an "XHTML5" document. Authors are reminded that the
processing for XML and HTML differs; in particular, even minor
syntax errors will prevent an XML document from being rendered
fully, whereas they would be ignored in the "HTML5" syntax.</p>

<p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
represent the same content. For example, namespaces cannot be
Expand Down Expand Up @@ -506,6 +506,12 @@
not an <span>ASCII case-insensitive</span> match for the string
"<code title="">xml</code>". <a href="#refsXML">[XML]</a></p>

<p>The term <dfn>XML MIME type</dfn> is used to refer to the MIME
types <code title="">text/xml</code>, <code
title="">application/xml</code>, and any MIME type ending with the
four characters "<code title="">+xml</code>". <a
href="#refsRFC3023">[RFC3023]</a></p>


<h4>DOM trees</h4>

Expand Down Expand Up @@ -916,8 +922,8 @@

<p id="authors-using-xhtml">XML documents that use elements or
attributes from the <span>HTML namespace</span> and that are served
over the wire (e.g. by HTTP) must be sent using an XML MIME type
such as <code>application/xml</code> or
over the wire (e.g. by HTTP) must be sent using an <span>XML MIME
type</span> such as <code>application/xml</code> or
<code>application/xhtml+xml</code> and must not be served as
<code>text/html</code>. <a href="#refsRFC3023">[RFC3023]</a></p>

Expand Down Expand Up @@ -4486,8 +4492,6 @@

<h4 id="content-type-sniffing">Determining the type of a resource</h4>

<!-- MIMESNIFF = http://tools.ietf.org/html/draft-abarth-mime-sniff -->

<p>The <dfn title="Content-Type">Content-Type metadata</dfn> of a
resource must be obtained and interpreted in a manner consistent
with the requirements of the Content-Type Processing Model
Expand Down Expand Up @@ -19451,7 +19455,8 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
<h4>The <dfn><code>embed</code></dfn> element</h4>

<!--
XXX we have all kinds of quirks we should define, as e.g. shown in:
we have all kinds of quirks we should define if they come up during
testing, as e.g. shown in:
http://mxr.mozilla.org/mozilla-central/source/layout/generic/nsObjectFrame.cpp
http://trac.webkit.org/browser/trunk/WebCore/html/HTMLEmbedElement.cpp
http://trac.webkit.org/browser/trunk/WebCore/rendering/RenderPartObject.cpp (updateWidget)
Expand Down Expand Up @@ -19594,20 +19599,17 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
<li>

<p>Otherwise, if the <span title="url-path">&lt;path&gt;</span>
component of the <span>URL</span> of the specified resource <!--
XXX before or after redirects? --> matches a pattern that a
<span>plugin</span> supports, then the <span>content's type</span>
is the type that that plugin can handle.</p>
component of the <span>URL</span> of the specified resource (after
any redirects) matches a pattern that a <span>plugin</span>
supports, then the <span>content's type</span> is the type that
that plugin can handle.</p>

<p class="example">For example, a plugin might say that it can
handle resources with <span title="url-path">&lt;path&gt;</span>
components that end with the four character string "<code
title="">.swf</code>".</p>

<p class="XXX">It would be better if browsers didn't do
extension sniffing like this, and only based their decision on the
actual contents of the resource. Couldn't we just apply the
<span>sniffed type of a resource</span> steps?</p>
<!-- it's sad that we have to do extension sniffing. sigh. -->

</li>

Expand Down Expand Up @@ -19933,7 +19935,7 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>


<dt>If the <var title="">resource type</var> is an <span>XML MIME
type</span><!-- XXX xref --></dt>
type</span></dt>
<dt>If the <var title="">resource type</var> is HTML</dt>
<dt>If the <var title="">resource type</var> does not start with
"<code>image/</code>"</dt>
Expand Down Expand Up @@ -58256,6 +58258,7 @@ style/default.css</pre>
title="navigate-html">HTML document</span> section, and abort
these steps.</dd>

<!-- an <span>XML MIME type</span> -->
<dt>Any type ending in "+xml"</dt>
<dt>"application/xml"</dt>
<dt>"text/xml"</dt>
Expand Down Expand Up @@ -58714,12 +58717,13 @@ style/default.css</pre>
attention. If there is no indicated part, then the user agent must
not scroll anywhere.</p>

<p><dfn>The indicated part of the document</dfn> is the one that
the fragment identifier, if any, identifies. The semantics of the
<p><dfn>The indicated part of the document</dfn> is the one that the
fragment identifier, if any, identifies. The semantics of the
fragment identifier in terms of mapping it to a specific DOM Node is
defined by the MIME type specification of the document's MIME Type
(for example, the processing of fragment identifiers for XML MIME
types is the responsibility of RFC3023).</p>
(for example, the processing of fragment identifiers for <span
title="XML MIME type">XML MIME types</span> is the responsibility of
RFC3023).</p>

<p>For HTML documents (and the <code>text/html</code> MIME type),
the following processing model must be followed to determine what
Expand Down Expand Up @@ -82655,6 +82659,7 @@ time:empty { binding: <i title="">time</i>; }</pre>

[IANACHARSET] http://www.iana.org/assignments/character-sets
[ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
[MIMESNIFF] http://tools.ietf.org/html/draft-abarth-mime-sniff
[RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
[SCSU] http://www.unicode.org/unicode/reports/tr6/
[SHIFTJIS] JIS X0208:1997
Expand Down

0 comments on commit 9e8c47b

Please sign in to comment.