Re: Navigation Algorithm Ambiguity

Hi Essam,

Essam K <essam.k@outlook.com>, 2015-05-15 19:48 +0000:
> Archived-At: <http://www.w3.org/mid/BAY181-W90D60424A64E064F26A07F0C70@phx.gbl>
> 
> Hi,
> 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?

That seems like something worth filing a spec bug for—

  https://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG&component=HTML5%20spec

-- 
Michael[tm] Smith https://people.w3.org/mike