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 28655 - Navigation Algorithm Ambiguity
Summary: Navigation Algorithm Ambiguity
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-18 20:18 UTC by Essam
Modified: 2016-04-27 21:09 UTC (History)
5 users (show)

See Also:


Attachments

Description Essam 2015-05-18 20:18:30 UTC
I would like to point out one thing that is not clear from the specification. In section 5.6 Browsing the Web(http://www.w3.org/TR/html5/browsers.html#browsing-the-web), if a user-agent is trying to grab a new HTML page that is not in cache (as per step 14 of the navigation algorithm) we will request to get that page using fetch algorithm(http://www.w3.org/TR/html5/infrastructure.html#fetch) which is executed in async mode. After initiating the request, the navigation algorithm in step 18 waits for few bytes to be available before moving on and the fetch algorithm is supposed to queue a task that will fill input byte stream and invoke html parser to do appropriate steps (http://www.w3.org/TR/html5/browsers.html#read-html). But HTML parser is created by queuing a task in step 23 of navigation algorithm. If fetch algorithm gets bytes before execution of step 23 how will it wait for creation of html parser? Will it spin the event loop?
Comment 1 Arron Eicholz 2016-04-27 21:09:38 UTC
HTML5.1 Bugzilla Bug Triage: Moved to Github issue: https://github.com/w3c/html/issues/282

To file additional issues please use the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new Thanks!