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 6037 - Elaborate on Web compat characteristics of task queue interaction
Summary: Elaborate on Web compat characteristics of task queue interaction
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-09-08 09:05 UTC by Henri Sivonen
Modified: 2010-10-04 14:49 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2008-09-08 09:05:08 UTC
In reference to about the 15 IRC lines starting at

The spec should probably say something sufficiently Web compatible about the dequeuing of tasks from the parser, timer and layout task queues relative to each other.

I'm not sure what exactly it should say, but my rough guess is that whenever layout runs, pending timers should fire as well before the parser runs again.
Comment 1 Ian 'Hixie' Hickson 2008-12-25 02:49:52 UTC
I don't want to require anything that isn't necessary here. Do we have any evidence that we need more detail than we already have? (Right now UAs can process as many tokens as they like and the invocation of setTimeout callbacks is not guaranteed to be prompt.)
Comment 2 Maciej Stachowiak 2010-03-14 13:15:40 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.