Bug with Masonry on scroll

i do not see your page – but it sounds very similar to that: https://kriesi.at/support/topic/shifting-a-masonry-gallery-image-to-the-left-when-scrolling-down-then-up/

i can see it too: but on firefox it is very rare – on Chrome and Safari i see it allways but not only on stages – on the other section i have this too.
You might even reduce the value of av-masonry-entry by a few tenths of a percent.

.av-masonry-col-3 .av-masonry-entry {
    width: 33.2%;
}

Maybe it’s because of your very nice Captions presentation

this is hard to test only with developer tools because i had to reload the page to see the effect.

Yesterday you haven’t activated the animation effect of the masonries. ( that delayed animation when masonry comes into viewport )
And yesterday i have the described “bug” even sometimes on the other sections too – which would not support your supposition of the reason for this.

the “come into viewport” is correlated to the waypoint script i think. You can set a trigger point that has to be passed before the animation starts.
F.e. an offset of 50% ( means if the element passes the half of the viewport height – the animation starts. But in the consequence – if there is not enough content under the element to observe – the trigger can not be passed.

For example: because waypoint script is allready implemented in enfold – we can use it for those scroll induced events
on this page here – look what happens to the green div when the footer comes 20% to viewport (80% offsetTop)
https://webers-testseite.de/pureinstall/brodes/

This is a combination of animate.css ( Link ) hinge.
If you see my custom script:

function scroll_up_down_change() {
if(is_page( array( 630))) {
?>
<script>
(function($) {
	$('#kontaktbutton').addClass('animated');
	var element_to_observe = $('#footer');
    element_to_observe.waypoint(function(direction) {
        if (direction == 'up') { $('#kontaktbutton').addClass('hinge'); }
        else { $('#kontaktbutton').removeClass('hinge'); }
        $('#kontaktbutton').toggleClass('hinge');
      	}, 
		{ offset: '80%' });
})(jQuery);
</script>
<?php
}
}
add_action('wp_footer', 'scroll_up_down_change', 30);

the observe element is: #footer – and the element to animate is : in this case that #kontaktbutton
So maybe we can influence the enfold script in a way that the trigger point is not at a low offset but on a higher one.

ps – i found a solution to change it on general via child-theme function:
all credits goes @mensmaximus : https://kriesi.at/support/topic/animations-trigger-too-late/#post-651948

you can do it as @mensmaximus described as external script or i think it could be done via child-theme functions.php as internal script.
Maybe this is nice – because you can load that with if clauses only on pages where you like to change it.

But i think because of the extra setting on masonry-entries.js – this is not influenced.
– just brainstorming now to found a child-theme solution on changing the offset value for masonries.