Thank you for the post, @selbekk~
For completeness, one can unobserve the ref in FadeInSection on unmount.
FadeInSection
React.useEffect(() => { const observer = new IntersectionObserver(entries => { entries.forEach(entry => { console.log(`entry`, entry, `is = ${entry.isIntersecting}`); setVisible(entry.isIntersecting); }); }); const { current } = domRef; observer.observe(current); // π return () => observer.unobserve(current); }, []);
I wasn't aware of this unobserve until running into the issue recently when I implemented my sticky components using IntersectionObserver, which had a memory leak.
unobserve
Here is the fork with unobserve & "unmount" button.
Ah thatβs true - forgot about that one! Iβll update the example later today to include it (with credit given, of course)
Edit: Updated the post.
Thank you π€
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for the post, @selbekk~
For completeness, one can unobserve the ref in
FadeInSection
on unmount.I wasn't aware of this
unobserve
until running into the issue recently when I implemented my sticky components using IntersectionObserver, which had a memory leak.Here is the fork with
unobserve
& "unmount" button.Ah thatβs true - forgot about that one! Iβll update the example later today to include it (with credit given, of course)
Edit: Updated the post.
Thank you π€