Chrome update compromising the viability of virtual scroll

Hello 👋 After my latest Google Chrome update, I’ve started noticing a really bad new feature.

Describe the bug From what I understand, content that is translated outside of the viewport is unmounted by the browser. Only for it the be rendered again once the content gets in the viewport.

For virtual-scroll, this means that the whole content of a page is constantly unmounted and rerendered. In theory, it shouldn’t be too bad, but the rerendering is pretty noticeable. What’s even more worrying is that content sometimes fails to be rerendered simply by entering the viewport. Meaning that whole pieces of UI can randomly go missing (until something is interacted with and forces the browser to rerender its view).

To Reproduce Steps to reproduce the behavior:

1. Go to https://locomotive.ca/en
2. Scroll down a bit
3. Scroll back up (the quicker the more obvious it is)

Expected behavior The content should not be unmounted when out of the viewport.

I’m aware this is not related to locomotive-scroll, but it impacts it nonetheless. I feel like we should report this issue to chrome or the viability of all virtual scroll library can be compromised.

Report issue:

1. chrome://settings/help
2. Report an issue

Desktop (please complete the following information):

• OS: Big Sur
• Browser: Chrome
• Version: v94.0.4606.81

Thank you 👊

[Dushyant1295]

Same Here, all my websites built with locomotive scroll complaining after Chrome update

html.has-scroll-smooth {
    overflow: hidden;
    position: fixed;
    left: 0;
    right: 0;
    top: 0;
    bottom: 0;  
}

By adding position:fixed works fine for now, but I’m not sure if it’s a perfect way to resolve this issue

[vitass]

Noticed the same a couple of days back - a temp fix would be to put a position: fixed on the wrapper. In case of the https://locomotive.ca/en would be to do it on [data-load-container].