Re: [spec-reviews] requestIdleCallback (#70)

So far our solution seems to be adding integration hooks at various allowed points, like animation frame tasks being exposed via requestAnimationFrame, or microtasks indirectly via promises. It seems reasonable to propose other APIs if you want, like requestResizeStep(fn), but of course doing so locks implementers more into a very specific model.

As for where it belongs, I don't think that's really important. Right now HTML defines the event loop, browsing context creation, and navigation. If someone besides the HTML editors wanted to take on those tasks and showed themselves to be good at it I imagine it would be fine to move the definition to their spec. It fits pretty naturally into HTML though given all the integration work.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/70#issuecomment-140497894