Discuss
  • Message History
Ian Hickson (2014-06-11T02:55:10.000Z)
On Tue, 10 Jun 2014, Allen Wirfs-Brock wrote:
> 
> Regarding, Domenic's and Boris responses, I don't see why ES6 promise 
> related Jobs need to be translated into HTML Tasks/Microtasks at all.  
> The ES6 spec. takes care of creating and queueing its promise related 
> Jobs.  The only thing HTML needs to worry about is specify when the ES 
> "PrimiseJobs" queue is serviced in relationship to any other ES Job 
> queues it may use.  That means the the HTML scheduling algorithm may 
> impose a scheduling priority of promise Jobs relative to various kinds 
> of HTML Tasks/MicroTask.  But it doesn't mean that that promise Jobs 
> have any of the other semantic characteristics of those HTML 
> abstractions.

Well presumably if promise resolution job "enqueings" are interleaved 
with, e.g., table sorting microtasks queueings, they'd need to be executed 
in that order. So at some point they need to actually interleave with 
non-ES-driven microtasks.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
domenic at domenicdenicola.com (2014-06-17T20:44:30.604Z)
On Tue, 10 Jun 2014, Allen Wirfs-Brock wrote:
> Regarding, Domenic's and Boris responses, I don't see why ES6 promise 
> related Jobs need to be translated into HTML Tasks/Microtasks at all.  
> The ES6 spec. takes care of creating and queueing its promise related 
> Jobs.  The only thing HTML needs to worry about is specify when the ES 
> "PrimiseJobs" queue is serviced in relationship to any other ES Job 
> queues it may use.  That means the the HTML scheduling algorithm may 
> impose a scheduling priority of promise Jobs relative to various kinds 
> of HTML Tasks/MicroTask.  But it doesn't mean that that promise Jobs 
> have any of the other semantic characteristics of those HTML 
> abstractions.

Well presumably if promise resolution job "enqueings" are interleaved 
with, e.g., table sorting microtasks queueings, they'd need to be executed 
in that order. So at some point they need to actually interleave with 
non-ES-driven microtasks.
Edit