Scroll into view quick animations on class are conflicting but only on some pages?


After creating the bare bones of a website, I decided to add some simple scroll in animations to various elements. I did this by configuring a few standard quick slide appear animation classes with different delays. e.g. “Speed300” is a slide in from the bottom with a 300 dealy. My theory this would be easy to just add a class to existing elements, then to add and reconfigure interactions settings for each class or element.

I then added these classes to various elements to stagger how they appear when you scroll down.

On my test page, it all worked fine and nothing conflicted. However, when applied to real elements on the home page, each time an element scrolls into view with a various animation class, it retriggers all other elements with that class. e.g. when an element with class “speed300” scrolls into view, all the other elements above it, with class “speed300”, that have already triggered, retrigger.

Not sure if this is me being super stupid but I’m confused why the test page doesn’t do this and the homepage does. Any help would be much appreciated.

My test page is named Scrolling test page, and home page, is home.



Here is my site Read-Only: LINK
(how to share your site Read-Only link)

Hi @Fred_Wordie

Thanks so much for posting about this.

I took a look at your sight but am a bit confused by the issue. It looks like the home page elements are scrolling into view as expected. When looking into your interactions, I saw both Interactions 2.0 and legacy IX, but I’m not sure which are being used for the test page vs the home page.

Have you resolved this? If not can you provide some screenshots/recordings showing the issue?

​Thanks in advance!

Hi Brando,

I got impatient and redid the animations form the ground up, everything is now working as expected.

I can go into my archive history if you like so you can see the bug?



Hi Fred, thanks for letting me know. I think we can mark this as resolved for the time being. If you run into the issue again, though, please let us know with a new forum post or through our contact form :slight_smile:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.