- From: <bugzilla@jessica.w3.org>
- Date: Tue, 19 Aug 2014 17:10:30 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26575 --- Comment #5 from Mark Watson <watsonm@netflix.com> --- (In reply to Domenic Denicola from comment #4) > > Is it not possible, in the existing model, to simply require that the promise MUST be resolved > > Sure > > > (and the resolution hander executed) > > Impossible; a handler can be added to the promise at any time. Ah, let me rephrase: could the specification require that strictly before any message event generated, the promise must be resolved and any resolution handler present *at the time of resolution* be executed ? When I say in the specification "resolve the promise", when does any handler present at that time get executed ? Right away ? Or is a task queued somewhere to execute that handler ? If a task is queued, then if I later say "queue a task to fire a simple event ..." can I be sure that this task is put into the same queue as the task to execute the resolution handler ? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 19 August 2014 17:10:32 UTC