question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chrome update compromising the viability of virtual scroll

See original GitHub issue

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 👊

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:32
  • Comments:15 (3 by maintainers)

github_iconTop GitHub Comments

22reactions
Dushyant1295commented, Nov 2, 2021

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

8reactions
vitasscommented, Oct 19, 2021

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].

Read more comments on GitHub >

github_iconTop Results From Across the Web

When scrolling up, some elements disappears (menu for ex.)
I feel like we should report this issue to chrome or the viability of all virtual scroll library can be compromised. Report issue:...
Read more >
Chrome scrolls more smoothly - Google Groups
I updated chrome today. I found it can scroll when i set a debuger in devtools, it did not happen before. We used...
Read more >
BROWSING AND SCROLLING ISSUES IN CHROME AFTER ...
Hi RAD, As a workaround to this issue. You may temporarily hide the update while we wait for our developers response regarding this...
Read more >
Google • Page 13 • Tag • The Register
That means no security updates, which puts users at risk of compromise ... harvesting our personal info even though we opted out of...
Read more >
Microsoft Limits Cortana To Bing Search, Edge Browser
As part of an OS update, Microsoft has restricted its personal digital assistant to ... Chrome, Firefox, and other third-party search engines and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found