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

I'm also satisfied with the conclusions. I only have a couple of minor bits of feedback:

1. The explainer notes at the beginning, that one of the ways developers workaround the lack of `queueMicrotask` is by (3) triggering custom element reactions. However, according to [the HTML spec](https://html.spec.whatwg.org/multipage/custom-elements.html#custom-element-reactions), custom element reactions do not actually use microtasks (they use the special "almost synchronous" nano-task concept). So, I'd like to see that assertion dropped from the explainer. I don't believe that we should consider a `queueNanotask` because such an API would invoke its callback nearly synchronously, which is really pretty pointless--rather the API would need to bind to some other action to be more useful, and at that point it's starting to look a lot like [`Object.observe`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/observe).

2. It would be nice to move the explainer into GitHub (WICG) and reformat as an HTML or MD file for improved discoverability.

-- 
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-414705856