The "initialization" steps for Web browsers

Allen Wirfs-Brock allen at
Tue Jun 10 15:45:54 PDT 2014

On Jun 10, 2014, at 2:33 PM, Ian Hickson wrote:

> On Tue, 10 Jun 2014, Domenic Denicola wrote:
>> Remember that ES tasks === HTML microtasks (in all implementations 
>> today [...]
> That doesn't sound right. If every script is always running on an ES task, 
> then it sounds like an ES task is neither an HTML task nor an HTML 
> microtask. A single HTML task might involve running multiple scripts (some 
> even nested inside each other, with microtasks firing after each of 
> those). For example, consider a task that changes a flag and then fires an 
> event; the event being fired is then handled by a number of event 
> listeners, each of which then fires an ES task to run the script, and 
> after each one there's the microtask queue is flushed, before finally 
> returning back to the main task, and then continuing the event loop.

Exactly, a ES Task (now Job) is just an atomic unit of ES code scheduling and executino.  I'm not in the business to telling host environments exactly how they should map their abstractions into such Jobs sized units. 


More information about the es-discuss mailing list