- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 16 Jun 2009 19:55:19 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv3978
Modified Files:
Overview.html
Log Message:
A variety of mostly editorial fixes: XML MIME type xref; resolve some minor issues for plugins, collect references. (whatwg r3284)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2430
retrieving revision 1.2431
diff -u -d -r1.2430 -r1.2431
--- Overview.html 16 Jun 2009 19:20:21 -0000 1.2430
+++ Overview.html 16 Jun 2009 19:55:16 -0000 1.2431
@@ -1267,13 +1267,13 @@
recommended for most authors. It is compatible with all legacy Web
browsers. If a document is transmitted with the MIME type <code title="">text/html</code>, then it will be processed as an "HTML5"
document by Web browsers.<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>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
+ "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>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
represent the same content. For example, namespaces cannot be
represented using "HTML5", but they are supported in "DOM5 HTML" and
"XHTML5". Similarly, documents that use the <code><a href="#the-noscript-element">noscript</a></code>
@@ -1396,7 +1396,9 @@
match the <a href="http://www.w3.org/TR/REC-xml/#NT-Name"><code title="">Name</code></a> production defined in XML, they contain no
U+003A COLON (:) characters, and their first three characters are
not an <a href="#ascii-case-insensitive">ASCII case-insensitive</a> match for the string
- "<code title="">xml</code>". <a href="#references">[XML]</a><h4 id="dom-trees"><span class="secno">2.1.2 </span>DOM trees</h4><p>The term <dfn id="root-element">root element</dfn>, when not explicitly qualified
+ "<code title="">xml</code>". <a href="#references">[XML]</a><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="#references">[RFC3023]</a><h4 id="dom-trees"><span class="secno">2.1.2 </span>DOM trees</h4><p>The term <dfn id="root-element">root element</dfn>, when not explicitly qualified
as referring to the document's root element, means the furthest
ancestor element node of whatever node is being discussed, or the
node itself if it has no ancestors. When the node is a part of the
@@ -1710,8 +1712,8 @@
may support only one of these two formats, although supporting both
is encouraged.</span><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="#references">[RFC3023]</a><p id="authors-using-html">Documents that use <a href="#syntax">the HTML
syntax</a>, if they are served over the wire (e.g. by HTTP) must
@@ -4353,8 +4355,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
@@ -15788,7 +15788,8 @@
context</a>.</p>
</div><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)
@@ -15910,19 +15911,16 @@
<li>
<p>Otherwise, if the <a href="#url-path" title="url-path"><path></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"><path></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>
@@ -16185,8 +16183,8 @@
</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>
@@ -45918,6 +45916,7 @@
<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>
@@ -46318,12 +46317,12 @@
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
@@ -63834,6 +63833,7 @@
[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
Received on Tuesday, 16 June 2009 19:55:27 UTC