W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2010

hixie: Talk about parsing tasks. (whatwg r4710)

From: poot <cvsmail@w3.org>
Date: Sun, 14 Feb 2010 13:10:06 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100214041007.2087E2BC93@toro.w3.mag.keio.ac.jp>
hixie: Talk about parsing tasks. (whatwg r4710)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3760&r2=1.3761&f=h
http://html5.org/tools/web-apps-tracker?from=4709&to=4710

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3760
retrieving revision 1.3761
diff -u -d -r1.3760 -r1.3761
--- Overview.html	14 Feb 2010 03:26:58 -0000	1.3760
+++ Overview.html	14 Feb 2010 04:09:48 -0000	1.3761
@@ -41431,11 +41431,16 @@
   <h4 id="read-html"><span class="secno">5.5.2 </span><dfn title="navigate-html">Page load processing model for HTML files</dfn></h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
 
   <p>When an HTML document is to be loaded in a <a href="#browsing-context">browsing
-  context</a>, the user agent must <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, and begin to use the
-  bytes provided for the document as the <a href="#the-input-stream">input stream</a> for
-  that parser.</p>
+  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>
 
   <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,
@@ -41445,7 +41450,8 @@
   <!-- next two paragraphs are nearly identical to the navigate-text
   section, keep them in sync -->
 
-  <p>When no more bytes are available, an EOF character is implied,
+  <p>When no more bytes are available, the user agent must <a href="#queue-a-task">queue
+  a task</a> for the parser to process the implied EOF character,
   which eventually causes a <code title="event-load">load</code> event
   to be fired.</p>
 
@@ -41458,6 +41464,8 @@
   cache selection</a> happens <a href="#parser-appcache">in the
   HTML parser</a>.</p>
 
+  <p>The <a href="#task-source">task source</a> for the two tasks mentioned in this
+  section must be the <a href="#networking-task-source">networking task source</a>.</p>
 
 
 
@@ -41520,15 +41528,19 @@
   <h4 id="read-text"><span class="secno">5.5.4 </span><dfn title="navigate-text">Page load processing model for text files</dfn></h4><p class="XXX annotation"><b>Status: </b><i>Implemented and widely deployed</i></p>
 
   <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="#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"
+  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-->, switch the <a href="#html-parser">HTML parser</a>'s tokenizer to
-  the <a href="#plaintext-state">PLAINTEXT state</a>, and begin to pass the stream of
-  characters in the plain text document to that tokenizer.</p>
+  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 are defined in RFC 2046, RFC 2646, and
@@ -41559,6 +41571,9 @@
   binding, providing script, giving the document a <code><a href="#the-title-element-0">title</a></code>,
   etc.</p>
 
+  <p>The <a href="#task-source">task source</a> for the two tasks mentioned in this
+  section must be the <a href="#networking-task-source">networking task source</a>.</p>
+
 
   <h4 id="read-image"><span class="secno">5.5.5 </span><dfn title="navigate-image">Page load processing model for images</dfn></h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
Received on Sunday, 14 February 2010 04:10:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:17 GMT