ViewportEnter doesn't fire properly...I think?

Hi @Jaosh, so… I’m from Wix Code QA. I assumed you’d found a weird bug and I was motivated to reproduce it. I spent a fair amount of time troubleshooting your site and also recreating a similar page on one of my test sites.

I see all the problems that you see on your site. But I cannot reproduce it on my own. The issue appears to be that the position of #loadMoreStrip is not being updated correctly when you scroll down on your page and more data loads. The #loadMoreStrip element is pushed down but its internal location apparently is not. You can see this yourself by scrolling down then scrolling back up — the onViewportEnter event triggers when you’ve reached where #loadMoreStrip used to be. I also saw the data warning, though I have no idea if it’s related in any way. It’s very strange.

On my recreated site, everything works as it should. I used all the same elements in exactly the same positions with a large database full of images, yet it works every time.

Unfortunately, I agree with Alvar: I would try recreating the page from scratch, re-add all the elements and re-attach to the dataset, then see what happens. If that doesn’t work, try using different data to see if that’s the problem.

I wish I could help more. But this really should work. Give it a go and let us know what happens.

Oh, wait, I’m seeing something weird about the way your site is loading… It appears to be using our old Viewer app.

I need to consult with my colleagues. That might affect the way everything is rendered, especially something processor-intensive like the repeater-data-scrolling stuff… I’ll get back to you.

Hi Jaosh, great news: I think your site is fixed, and the bug no longer appears! The problem apparently was that the site contained an old Wix app that is no longer supported (eCom) and it was forcing the site to render using our old viewer technology. One of our developers removed the old app and your site immediately started using our newer viewer, which is much faster and more stable.

This is the reason no one else was able to reproduce the problem — we were all getting the new viewer while your site was getting the old viewer. Please try it now and confirm that it is fixed. Good luck!

Great news!

Thanks a lot.

Hope it worked :grinning:

Ty for taking the time out to solve this Chaim!!

Really pulled out my hair trying to figure this out.