Closed jlmakes closed 6 years ago
I can reproduce this using JSBin, but not in my local environment! (Argh!)
From my tinkering, it seems the ScrollReveal store is being nuked by clean()
or destroy()
midway through looping over elements, so isElementVisible()
attempts to access element
and container
data that no longer exists.
ScrollReveal v4.0.0-beta.6
The
sr.clean(selector)
works as intended (deleting elements and unbinding event handlers), but if called during scroll can remove elements that are still being worked on by the last call of the event handler.