Re: [w3ctag/design-reviews] TAG Review Request: queueMicrotask (#294)

@slightlyoff 

Re: Arguments - I've updated the explainer to include Domenic's justifications.

Re: example for using this vs alternatives - I've rewritten the motivation section. There are 2 things I could be explaining:
  - when to use microtask vs task vs RAF
  - why we want to make queueMicrotask an API

Previously the doc was a mix of both. It's now focused on the latter (but includes a link to another article that explains more about the former). Viewed in that way, there are no reasonable alternatives, if you want to queue a microtask you should call `queueMicrotask()`, there is no scenario where you should still consider `Promise.resolve().then()` (assuming you're on a browser that supports it).

If you feel strongly that the doc needs to explain more about what a microtask is and when it's the right choice, I can add that but it seems secondary.

Re: other timings that should be exposed - I defer to others on that.

@dbaron Cancellation seems reasonable to me. @domenic any opinions on that?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/294#issuecomment-408295148