pull down to refresh
reply
You probably told it to run after hydration, and that’s what it did, haha
But when we don’t remove the node, we don’t interfere with hydration, so we don’t need to run it after hydration.
Edit: But sounded like it was still broken after the first prompt, so you prompted it again, and that contained the actual, inspiring fix via CSS haha
With
node.style = "display: none", you can also keep running it after the slightly fasterDOMContentLoadedevent and don't needrequestAnimationFrame. Theloadevent will also wait until images are loaded.Thank you!!