This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8825 - "begin to use the bytes provided for the document as the input stream for that parser" is way too vague -- it should relate to the parsing tasks mentioned in the event loop section ("one per byte" etc)
Summary: "begin to use the bytes provided for the document as the input stream for tha...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-27 10:19 UTC by contributor
Modified: 2010-10-04 14:46 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-01-27 10:19:51 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#read-html

Comment:
"begin to use the bytes provided for the document as the input stream for that
parser" is way too vague -- it should relate to the parsing tasks mentioned in
the event loop section ("one per byte" etc)

Posted from: 98.248.33.53
Comment 1 Henri Sivonen 2010-01-27 10:26:32 UTC 
Please make sure that parsing the empty stream is allowed to take two main event loop tasks.

Currently, in Gecko with the HTML5 parser, one task does the initial setup and there's always another task that pushes the EOF through. Changing this would be a pain.
Comment 2 Ian 'Hixie' Hickson 2010-02-14 04:09:18 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: see diff given below
Rationale: I've tried to twist the text into making more sense.
Comment 3 contributor 2010-02-14 04:09:59 UTC 
Checked in as WHATWG revision r4710.
Check-in comment: Talk about parsing tasks.
http://html5.org/tools/web-apps-tracker?from=4709&to=4710
Comment 4 contributor 2010-02-14 04:11:55 UTC 
Checked in as WHATWG revision r4711.
Check-in comment: Talk about parsing tasks. (missed one change)
http://html5.org/tools/web-apps-tracker?from=4710&to=4711