Re: [whatwg/webidl] Record timing info for promise resolve/reject and callback (PR #1400)

> They'd both get attributed to the event handler as the JS stack will be non-empty by the time you get to the promise though.

That's not true, as firing an event clears the microtask queue (in "cleanup after script").

> I think it also gets confusing if you resolve multiple promises in a single task.

Sure, though that's a rare case.

> I don't like using "resolve" and "reject" as entry points coupled with the JS stack being empty as in my mind that's very much against the way promises are designed. Tying this directly to tasks (that may execute script) seems much more natural.

See above, this would lose important information if you do other things in that task.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/pull/1400#issuecomment-2228625848
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1400/c2228625848@github.com>