[html5] r6515 - [giow] (0) DOM Core compatibility (Document.contentType values) Fixing http://ww [...]

whatwg at whatwg.org whatwg at whatwg.org
Thu Aug 18 21:15:20 PDT 2011


Author: ianh
Date: 2011-08-18 21:15:18 -0700 (Thu, 18 Aug 2011)
New Revision: 6515

Modified:
   complete.html
   index
   source
Log:
[giow] (0) DOM Core compatibility (Document.contentType values)
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13138

Modified: complete.html
===================================================================
--- complete.html	2011-08-19 02:58:21 UTC (rev 6514)
+++ complete.html	2011-08-19 04:15:18 UTC (rev 6515)
@@ -3792,7 +3792,7 @@
 
      <li><dfn id=dom-event-target title=dom-Event-target><code>target</code></dfn> attribute</li>
 
-     <li>The <dfn id="document's-character-encoding" title="document's character encoding">character encoding</dfn> of a <code><a href=#document>Document</a></code></li>
+     <li>The <dfn id="document's-character-encoding" title="document's character encoding">character encoding</dfn> and <span title=concept-document-media-type>media type</span> of a <code><a href=#document>Document</a></code></li>
      <li>The distinction between <dfn id=xml-documents>XML documents</dfn> and <dfn id=html-documents>HTML documents</dfn></li>
      <li>The terms <dfn id=quirks-mode>quirks mode</dfn>, <dfn id=limited-quirks-mode>limited-quirks mode</dfn>, and <dfn id=no-quirks-mode>no-quirks mode</dfn></li>
      <li>The algorithm to <dfn id=concept-node-clone title=concept-node-clone>clone</dfn> a <code><a href=#node>Node</a></code>, and the concept of <dfn id=concept-node-clone-ext title=concept-node-clone-ext>cloning steps</dfn> used by tat algorithm</li>
@@ -64804,14 +64804,12 @@
   <p>When an HTML document is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent must <a href=#queue-a-task>queue a task</a> to
   <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it as being
-  an <a href=#html-documents title="HTML documents">HTML document</a>, create an
-  <a href=#html-parser>HTML parser</a>, and associate it with the document. Each
-  <a href=#concept-task title=concept-task>task</a> that the <a href=#networking-task-source>networking
-  task source</a> places on the <a href=#task-queue>task queue</a> while the
-  <a href=#fetch title=fetch>fetching algorithm</a> runs must then fill
-  the parser's <a href=#the-input-stream>input stream</a> with the fetched bytes and
-  cause the <a href=#html-parser>HTML parser</a> to perform the appropriate
-  processing of the input stream.</p>
+  an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to "<code title="">text/html</code>", create an <a href=#html-parser>HTML parser</a>, and
+  associate it with the document. Each <a href=#concept-task title=concept-task>task</a> that the <a href=#networking-task-source>networking task
+  source</a> places on the <a href=#task-queue>task queue</a> while the <a href=#fetch title=fetch>fetching algorithm</a> runs must then fill the
+  parser's <a href=#the-input-stream>input stream</a> with the fetched bytes and cause
+  the <a href=#html-parser>HTML parser</a> to perform the appropriate processing
+  of the input stream.</p>
 
   <p class=note>The <a href=#the-input-stream>input stream</a> converts bytes into
   characters for use in the <a href=#tokenization title=tokenization>tokenizer</a>. This process relies, in part,
@@ -64845,7 +64843,7 @@
   <p>When faced with displaying an XML file inline, user agents must
   first <a href=#create-a-document-object>create a <code>Document</code> object</a>, following
   the requirements of the XML and Namespaces in XML recommendations,
-  RFC 3023, DOM3 Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOMCORE>[DOMCORE]</a></p>
+  RFC 3023, DOM Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOMCORE>[DOMCORE]</a></p>
 
   <p>The actual HTTP headers and other metadata, not the headers as
   mutated or implied by the algorithms given in this specification,
@@ -64904,17 +64902,18 @@
   <p>When a plain text document is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent should <a href=#queue-a-task>queue a task</a> to
   <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it as being
-  an <a href=#html-documents title="HTML documents">HTML document</a>, create an
-  <a href=#html-parser>HTML parser</a>, associate it with the document, act as if
-  the tokenizer had emitted a start tag token with the tag name "pre"
-  followed by a single U+000A LINE FEED (LF) character<!-- to get
-  eaten, so that a leading LF in the text/plain stream doesn't get
-  eaten itself-->, and switch the <a href=#html-parser>HTML parser</a>'s tokenizer
-  to the <a href=#plaintext-state>PLAINTEXT state</a>.  Each <a href=#concept-task title=concept-task>task</a> that the <a href=#networking-task-source>networking task
-  source</a> places on the <a href=#task-queue>task queue</a> while the <a href=#fetch title=fetch>fetching algorithm</a> runs must then fill the
-  parser's <a href=#the-input-stream>input stream</a> with the fetched bytes and cause
-  the <a href=#html-parser>HTML parser</a> to perform the appropriate processing
-  of the input stream.</p>
+  an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to "<code title="">text/plain</code>", create an <a href=#html-parser>HTML parser</a>,
+  associate it with the document, act as if the tokenizer had emitted
+  a start tag token with the tag name "pre" followed by a single
+  U+000A LINE FEED (LF) character<!-- to get eaten, so that a leading
+  LF in the text/plain stream doesn't get eaten itself-->, and switch
+  the <a href=#html-parser>HTML parser</a>'s tokenizer to the <a href=#plaintext-state>PLAINTEXT
+  state</a>. Each <a href=#concept-task title=concept-task>task</a> that the
+  <a href=#networking-task-source>networking task source</a> places on the <a href=#task-queue>task
+  queue</a> while the <a href=#fetch title=fetch>fetching algorithm</a>
+  runs must then fill the parser's <a href=#the-input-stream>input stream</a> with the
+  fetched bytes and cause the <a href=#html-parser>HTML parser</a> to perform the
+  appropriate processing of the input stream.</p>
 
   <p>The rules for how to convert the bytes of the plain text document
   into actual characters, and the rules for actually rendering the
@@ -64961,12 +64960,14 @@
 
   <p>When an image resource is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent should <a href=#create-a-document-object>create a
-  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, append an
-  <code><a href=#the-html-element>html</a></code> element to the <code><a href=#document>Document</a></code>, append a
-  <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element to the
-  <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-img-element>img</a></code> to the
-  <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute of the <code><a href=#the-img-element>img</a></code>
-  element to the address of the image.</p>
+  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to the sniffed
+  MIME type of the resource (<var title="">type</var> in the
+  <a href=#navigate>navigate</a> algorithm), append an <code><a href=#the-html-element>html</a></code>
+  element to the <code><a href=#document>Document</a></code>, append a <code><a href=#the-head-element>head</a></code>
+  element and a <code><a href=#the-body-element>body</a></code> element to the <code><a href=#the-html-element>html</a></code>
+  element, append an <code><a href=#the-img-element>img</a></code> to the <code><a href=#the-body-element>body</a></code>
+  element, and set the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute
+  of the <code><a href=#the-img-element>img</a></code> element to the address of the image.</p>
 
   <!-- next three paragraphs are similar to the navigate-text section,
   keep them in sync -->
@@ -64994,12 +64995,16 @@
   <p>When a resource that requires an external resource to be rendered
   is to be loaded in a <a href=#browsing-context>browsing context</a>, the user agent
   should <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it
-  as being an <a href=#html-documents title="HTML documents">HTML document</a>,
-  append an <code><a href=#the-html-element>html</a></code> element to the <code><a href=#document>Document</a></code>,
-  append a <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element
-  to the <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-embed-element>embed</a></code> to
-  the <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute of the
-  <code><a href=#the-embed-element>embed</a></code> element to the address of the resource.</p>
+  as being an <a href=#html-documents title="HTML documents">HTML document</a>, set
+  its <span title=concept-document-media-type>media type</span> to
+  the sniffed MIME type of the resource (<var title="">type</var> in
+  the <a href=#navigate>navigate</a> algorithm), append an <code><a href=#the-html-element>html</a></code>
+  element to the <code><a href=#document>Document</a></code>, append a <code><a href=#the-head-element>head</a></code>
+  element and a <code><a href=#the-body-element>body</a></code> element to the <code><a href=#the-html-element>html</a></code>
+  element, append an <code><a href=#the-embed-element>embed</a></code> to the <code><a href=#the-body-element>body</a></code>
+  element, and set the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code>
+  attribute of the <code><a href=#the-embed-element>embed</a></code> element to the address of the
+  resource.</p>
 
   <!-- next three paragraphs are similar to the navigate-text section,
   keep them in sync -->
@@ -65031,11 +65036,11 @@
 
   <p>When the user agent is to display a user agent page inline in a
   <a href=#browsing-context>browsing context</a>, the user agent should <a href=#create-a-document-object>create a
-  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, and then either
-  associate that <code><a href=#document>Document</a></code> with a custom rendering that is
-  not rendered using the normal <code><a href=#document>Document</a></code> rendering rules,
-  or mutate that <code><a href=#document>Document</a></code> until it represents the content
-  the user agent wants to render.</p>
+  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to "<code title="">text/html</code>", and then either associate that
+  <code><a href=#document>Document</a></code> with a custom rendering that is not rendered
+  using the normal <code><a href=#document>Document</a></code> rendering rules, or mutate
+  that <code><a href=#document>Document</a></code> until it represents the content the user
+  agent wants to render.</p>
 
   <!-- next two paragraphs are similar to the navigate-text section,
   keep them in sync -->

Modified: index
===================================================================
--- index	2011-08-19 02:58:21 UTC (rev 6514)
+++ index	2011-08-19 04:15:18 UTC (rev 6515)
@@ -3689,7 +3689,7 @@
 
      <li><dfn id=dom-event-target title=dom-Event-target><code>target</code></dfn> attribute</li>
 
-     <li>The <dfn id="document's-character-encoding" title="document's character encoding">character encoding</dfn> of a <code><a href=#document>Document</a></code></li>
+     <li>The <dfn id="document's-character-encoding" title="document's character encoding">character encoding</dfn> and <span title=concept-document-media-type>media type</span> of a <code><a href=#document>Document</a></code></li>
      <li>The distinction between <dfn id=xml-documents>XML documents</dfn> and <dfn id=html-documents>HTML documents</dfn></li>
      <li>The terms <dfn id=quirks-mode>quirks mode</dfn>, <dfn id=limited-quirks-mode>limited-quirks mode</dfn>, and <dfn id=no-quirks-mode>no-quirks mode</dfn></li>
      <li>The algorithm to <dfn id=concept-node-clone title=concept-node-clone>clone</dfn> a <code><a href=#node>Node</a></code>, and the concept of <dfn id=concept-node-clone-ext title=concept-node-clone-ext>cloning steps</dfn> used by tat algorithm</li>
@@ -64671,14 +64671,12 @@
   <p>When an HTML document is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent must <a href=#queue-a-task>queue a task</a> to
   <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it as being
-  an <a href=#html-documents title="HTML documents">HTML document</a>, create an
-  <a href=#html-parser>HTML parser</a>, and associate it with the document. Each
-  <a href=#concept-task title=concept-task>task</a> that the <a href=#networking-task-source>networking
-  task source</a> places on the <a href=#task-queue>task queue</a> while the
-  <a href=#fetch title=fetch>fetching algorithm</a> runs must then fill
-  the parser's <a href=#the-input-stream>input stream</a> with the fetched bytes and
-  cause the <a href=#html-parser>HTML parser</a> to perform the appropriate
-  processing of the input stream.</p>
+  an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to "<code title="">text/html</code>", create an <a href=#html-parser>HTML parser</a>, and
+  associate it with the document. Each <a href=#concept-task title=concept-task>task</a> that the <a href=#networking-task-source>networking task
+  source</a> places on the <a href=#task-queue>task queue</a> while the <a href=#fetch title=fetch>fetching algorithm</a> runs must then fill the
+  parser's <a href=#the-input-stream>input stream</a> with the fetched bytes and cause
+  the <a href=#html-parser>HTML parser</a> to perform the appropriate processing
+  of the input stream.</p>
 
   <p class=note>The <a href=#the-input-stream>input stream</a> converts bytes into
   characters for use in the <a href=#tokenization title=tokenization>tokenizer</a>. This process relies, in part,
@@ -64712,7 +64710,7 @@
   <p>When faced with displaying an XML file inline, user agents must
   first <a href=#create-a-document-object>create a <code>Document</code> object</a>, following
   the requirements of the XML and Namespaces in XML recommendations,
-  RFC 3023, DOM3 Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOMCORE>[DOMCORE]</a></p>
+  RFC 3023, DOM Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOMCORE>[DOMCORE]</a></p>
 
   <p>The actual HTTP headers and other metadata, not the headers as
   mutated or implied by the algorithms given in this specification,
@@ -64771,17 +64769,18 @@
   <p>When a plain text document is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent should <a href=#queue-a-task>queue a task</a> to
   <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it as being
-  an <a href=#html-documents title="HTML documents">HTML document</a>, create an
-  <a href=#html-parser>HTML parser</a>, associate it with the document, act as if
-  the tokenizer had emitted a start tag token with the tag name "pre"
-  followed by a single U+000A LINE FEED (LF) character<!-- to get
-  eaten, so that a leading LF in the text/plain stream doesn't get
-  eaten itself-->, and switch the <a href=#html-parser>HTML parser</a>'s tokenizer
-  to the <a href=#plaintext-state>PLAINTEXT state</a>.  Each <a href=#concept-task title=concept-task>task</a> that the <a href=#networking-task-source>networking task
-  source</a> places on the <a href=#task-queue>task queue</a> while the <a href=#fetch title=fetch>fetching algorithm</a> runs must then fill the
-  parser's <a href=#the-input-stream>input stream</a> with the fetched bytes and cause
-  the <a href=#html-parser>HTML parser</a> to perform the appropriate processing
-  of the input stream.</p>
+  an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to "<code title="">text/plain</code>", create an <a href=#html-parser>HTML parser</a>,
+  associate it with the document, act as if the tokenizer had emitted
+  a start tag token with the tag name "pre" followed by a single
+  U+000A LINE FEED (LF) character<!-- to get eaten, so that a leading
+  LF in the text/plain stream doesn't get eaten itself-->, and switch
+  the <a href=#html-parser>HTML parser</a>'s tokenizer to the <a href=#plaintext-state>PLAINTEXT
+  state</a>. Each <a href=#concept-task title=concept-task>task</a> that the
+  <a href=#networking-task-source>networking task source</a> places on the <a href=#task-queue>task
+  queue</a> while the <a href=#fetch title=fetch>fetching algorithm</a>
+  runs must then fill the parser's <a href=#the-input-stream>input stream</a> with the
+  fetched bytes and cause the <a href=#html-parser>HTML parser</a> to perform the
+  appropriate processing of the input stream.</p>
 
   <p>The rules for how to convert the bytes of the plain text document
   into actual characters, and the rules for actually rendering the
@@ -64828,12 +64827,14 @@
 
   <p>When an image resource is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent should <a href=#create-a-document-object>create a
-  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, append an
-  <code><a href=#the-html-element>html</a></code> element to the <code><a href=#document>Document</a></code>, append a
-  <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element to the
-  <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-img-element>img</a></code> to the
-  <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute of the <code><a href=#the-img-element>img</a></code>
-  element to the address of the image.</p>
+  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to the sniffed
+  MIME type of the resource (<var title="">type</var> in the
+  <a href=#navigate>navigate</a> algorithm), append an <code><a href=#the-html-element>html</a></code>
+  element to the <code><a href=#document>Document</a></code>, append a <code><a href=#the-head-element>head</a></code>
+  element and a <code><a href=#the-body-element>body</a></code> element to the <code><a href=#the-html-element>html</a></code>
+  element, append an <code><a href=#the-img-element>img</a></code> to the <code><a href=#the-body-element>body</a></code>
+  element, and set the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute
+  of the <code><a href=#the-img-element>img</a></code> element to the address of the image.</p>
 
   <!-- next three paragraphs are similar to the navigate-text section,
   keep them in sync -->
@@ -64861,12 +64862,16 @@
   <p>When a resource that requires an external resource to be rendered
   is to be loaded in a <a href=#browsing-context>browsing context</a>, the user agent
   should <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it
-  as being an <a href=#html-documents title="HTML documents">HTML document</a>,
-  append an <code><a href=#the-html-element>html</a></code> element to the <code><a href=#document>Document</a></code>,
-  append a <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element
-  to the <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-embed-element>embed</a></code> to
-  the <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute of the
-  <code><a href=#the-embed-element>embed</a></code> element to the address of the resource.</p>
+  as being an <a href=#html-documents title="HTML documents">HTML document</a>, set
+  its <span title=concept-document-media-type>media type</span> to
+  the sniffed MIME type of the resource (<var title="">type</var> in
+  the <a href=#navigate>navigate</a> algorithm), append an <code><a href=#the-html-element>html</a></code>
+  element to the <code><a href=#document>Document</a></code>, append a <code><a href=#the-head-element>head</a></code>
+  element and a <code><a href=#the-body-element>body</a></code> element to the <code><a href=#the-html-element>html</a></code>
+  element, append an <code><a href=#the-embed-element>embed</a></code> to the <code><a href=#the-body-element>body</a></code>
+  element, and set the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code>
+  attribute of the <code><a href=#the-embed-element>embed</a></code> element to the address of the
+  resource.</p>
 
   <!-- next three paragraphs are similar to the navigate-text section,
   keep them in sync -->
@@ -64898,11 +64903,11 @@
 
   <p>When the user agent is to display a user agent page inline in a
   <a href=#browsing-context>browsing context</a>, the user agent should <a href=#create-a-document-object>create a
-  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, and then either
-  associate that <code><a href=#document>Document</a></code> with a custom rendering that is
-  not rendered using the normal <code><a href=#document>Document</a></code> rendering rules,
-  or mutate that <code><a href=#document>Document</a></code> until it represents the content
-  the user agent wants to render.</p>
+  <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, set its <span title=concept-document-media-type>media type</span> to "<code title="">text/html</code>", and then either associate that
+  <code><a href=#document>Document</a></code> with a custom rendering that is not rendered
+  using the normal <code><a href=#document>Document</a></code> rendering rules, or mutate
+  that <code><a href=#document>Document</a></code> until it represents the content the user
+  agent wants to render.</p>
 
   <!-- next two paragraphs are similar to the navigate-text section,
   keep them in sync -->

Modified: source
===================================================================
--- source	2011-08-19 02:58:21 UTC (rev 6514)
+++ source	2011-08-19 04:15:18 UTC (rev 6515)
@@ -2693,7 +2693,7 @@
 
      <li><dfn title="dom-Event-target"><code>target</code></dfn> attribute</li>
 
-     <li>The <dfn title="document's character encoding">character encoding</dfn> of a <code>Document</code></li>
+     <li>The <dfn title="document's character encoding">character encoding</dfn> and <span title="concept-document-media-type">media type</span> of a <code>Document</code></li>
      <li>The distinction between <dfn>XML documents</dfn> and <dfn>HTML documents</dfn></li>
      <li>The terms <dfn>quirks mode</dfn>, <dfn>limited-quirks mode</dfn>, and <dfn>no-quirks mode</dfn></li>
      <li>The algorithm to <dfn title="concept-node-clone">clone</dfn> a <code>Node</code>, and the concept of <dfn title="concept-node-clone-ext">cloning steps</dfn> used by tat algorithm</li>
@@ -73555,14 +73555,16 @@
   <p>When an HTML document is to be loaded in a <span>browsing
   context</span>, the user agent must <span>queue a task</span> to
   <span>create a <code>Document</code> object</span>, mark it as being
-  an <span title="HTML documents">HTML document</span>, create an
-  <span>HTML parser</span>, and associate it with the document. Each
-  <span title="concept-task">task</span> that the <span>networking
-  task source</span> places on the <span>task queue</span> while the
-  <span title="fetch">fetching algorithm</span> runs must then fill
-  the parser's <span>input stream</span> with the fetched bytes and
-  cause the <span>HTML parser</span> to perform the appropriate
-  processing of the input stream.</p>
+  an <span title="HTML documents">HTML document</span>, set its <span
+  title="concept-document-media-type">media type</span> to "<code
+  title="">text/html</code>", create an <span>HTML parser</span>, and
+  associate it with the document. Each <span
+  title="concept-task">task</span> that the <span>networking task
+  source</span> places on the <span>task queue</span> while the <span
+  title="fetch">fetching algorithm</span> runs must then fill the
+  parser's <span>input stream</span> with the fetched bytes and cause
+  the <span>HTML parser</span> to perform the appropriate processing
+  of the input stream.</p>
 
   <p class="note">The <span>input stream</span> converts bytes into
   characters for use in the <span
@@ -73598,7 +73600,7 @@
   <p>When faced with displaying an XML file inline, user agents must
   first <span>create a <code>Document</code> object</span>, following
   the requirements of the XML and Namespaces in XML recommendations,
-  RFC 3023, DOM3 Core, and other relevant specifications. <a
+  RFC 3023, DOM Core, and other relevant specifications. <a
   href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a> <a
   href="#refsRFC3023">[RFC3023]</a> <a
   href="#refsDOMCORE">[DOMCORE]</a></p>
@@ -73666,19 +73668,20 @@
   <p>When a plain text document is to be loaded in a <span>browsing
   context</span>, the user agent should <span>queue a task</span> to
   <span>create a <code>Document</code> object</span>, mark it as being
-  an <span title="HTML documents">HTML document</span>, create an
-  <span>HTML parser</span>, associate it with the document, act as if
-  the tokenizer had emitted a start tag token with the tag name "pre"
-  followed by a single U+000A LINE FEED (LF) character<!-- to get
-  eaten, so that a leading LF in the text/plain stream doesn't get
-  eaten itself-->, and switch the <span>HTML parser</span>'s tokenizer
-  to the <span>PLAINTEXT state</span>.  Each <span
-  title="concept-task">task</span> that the <span>networking task
-  source</span> places on the <span>task queue</span> while the <span
-  title="fetch">fetching algorithm</span> runs must then fill the
-  parser's <span>input stream</span> with the fetched bytes and cause
-  the <span>HTML parser</span> to perform the appropriate processing
-  of the input stream.</p>
+  an <span title="HTML documents">HTML document</span>, set its <span
+  title="concept-document-media-type">media type</span> to "<code
+  title="">text/plain</code>", create an <span>HTML parser</span>,
+  associate it with the document, act as if the tokenizer had emitted
+  a start tag token with the tag name "pre" followed by a single
+  U+000A LINE FEED (LF) character<!-- to get eaten, so that a leading
+  LF in the text/plain stream doesn't get eaten itself-->, and switch
+  the <span>HTML parser</span>'s tokenizer to the <span>PLAINTEXT
+  state</span>. Each <span title="concept-task">task</span> that the
+  <span>networking task source</span> places on the <span>task
+  queue</span> while the <span title="fetch">fetching algorithm</span>
+  runs must then fill the parser's <span>input stream</span> with the
+  fetched bytes and cause the <span>HTML parser</span> to perform the
+  appropriate processing of the input stream.</p>
 
   <p>The rules for how to convert the bytes of the plain text document
   into actual characters, and the rules for actually rendering the
@@ -73728,13 +73731,15 @@
   <p>When an image resource is to be loaded in a <span>browsing
   context</span>, the user agent should <span>create a
   <code>Document</code> object</span>, mark it as being an <span
-  title="HTML documents">HTML document</span>, append an
-  <code>html</code> element to the <code>Document</code>, append a
-  <code>head</code> element and a <code>body</code> element to the
-  <code>html</code> element, append an <code>img</code> to the
-  <code>body</code> element, and set the <code
-  title="attr-img-src">src</code> attribute of the <code>img</code>
-  element to the address of the image.</p>
+  title="HTML documents">HTML document</span>, set its <span
+  title="concept-document-media-type">media type</span> to the sniffed
+  MIME type of the resource (<var title="">type</var> in the
+  <span>navigate</span> algorithm), append an <code>html</code>
+  element to the <code>Document</code>, append a <code>head</code>
+  element and a <code>body</code> element to the <code>html</code>
+  element, append an <code>img</code> to the <code>body</code>
+  element, and set the <code title="attr-img-src">src</code> attribute
+  of the <code>img</code> element to the address of the image.</p>
 
   <!-- next three paragraphs are similar to the navigate-text section,
   keep them in sync -->
@@ -73762,13 +73767,16 @@
   <p>When a resource that requires an external resource to be rendered
   is to be loaded in a <span>browsing context</span>, the user agent
   should <span>create a <code>Document</code> object</span>, mark it
-  as being an <span title="HTML documents">HTML document</span>,
-  append an <code>html</code> element to the <code>Document</code>,
-  append a <code>head</code> element and a <code>body</code> element
-  to the <code>html</code> element, append an <code>embed</code> to
-  the <code>body</code> element, and set the <code
-  title="attr-embed-src">src</code> attribute of the
-  <code>embed</code> element to the address of the resource.</p>
+  as being an <span title="HTML documents">HTML document</span>, set
+  its <span title="concept-document-media-type">media type</span> to
+  the sniffed MIME type of the resource (<var title="">type</var> in
+  the <span>navigate</span> algorithm), append an <code>html</code>
+  element to the <code>Document</code>, append a <code>head</code>
+  element and a <code>body</code> element to the <code>html</code>
+  element, append an <code>embed</code> to the <code>body</code>
+  element, and set the <code title="attr-embed-src">src</code>
+  attribute of the <code>embed</code> element to the address of the
+  resource.</p>
 
   <!-- next three paragraphs are similar to the navigate-text section,
   keep them in sync -->
@@ -73802,11 +73810,13 @@
   <p>When the user agent is to display a user agent page inline in a
   <span>browsing context</span>, the user agent should <span>create a
   <code>Document</code> object</span>, mark it as being an <span
-  title="HTML documents">HTML document</span>, and then either
-  associate that <code>Document</code> with a custom rendering that is
-  not rendered using the normal <code>Document</code> rendering rules,
-  or mutate that <code>Document</code> until it represents the content
-  the user agent wants to render.</p>
+  title="HTML documents">HTML document</span>, set its <span
+  title="concept-document-media-type">media type</span> to "<code
+  title="">text/html</code>", and then either associate that
+  <code>Document</code> with a custom rendering that is not rendered
+  using the normal <code>Document</code> rendering rules, or mutate
+  that <code>Document</code> until it represents the content the user
+  agent wants to render.</p>
 
   <!-- next two paragraphs are similar to the navigate-text section,
   keep them in sync -->




More information about the Commit-Watchers mailing list