Julien Pradet

> As far as I know, `requestIdleCallback` isn't the best place to do DOM work ([reference](https://developers.google.com/web/updates/2015/08/using-requestidlecallback#using_requestidlecallback_to_make_dom_changes)). We could use a requestAnimationFrame loop, but we'd need to determine the element's position...

Here are 4 timelines demonstrating the difference between `requestAnimationFrame` and `requestIdleCallback`. The red overlay indicates when the mouse is moving (identified by the additional JS performing in the 'main' timeline)....

Hi @YasserKaddour, I haven't gone any farther since I didn't know if my suggested solution would be merged (for lib size + lib goals reasons). Plus, there are two solutions...

Oops, nevermind for my fix. It has compatibility issues. I'll try to come up with a different one, but the bug is still relevant.

Hi! Thanks for the feedback. Currently, it's not really usable by anyone actually :sweat_smile: There's not even an npm package published yet. That's fun because there's been a few persons...

Hi! Thanks for the suggestion. I'll merge it later in the week end by adding other Svelte SSGs that I am aware of. I wouldn't feel at ease to reference...

Would you consider a PR that would tackle `renderAsync` that handles `{#await}` but without the streaming approach ? The reason I'm suggesting this is because I don't know how to...

This is actually exposed (didn't check if this is a new API or not but I'm in 2.20.1). What you have to do is: * iframe has `allow="fullscreen"` (in my...