-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome update compromising the viability of virtual scroll #353
Comments
Hello fcisio I'm using locomotive scroll on wordpress using oh boiii steroids plugin and since saturday it's a mess. I think for now I will have to delete it completly :( When I look at others website made with locomotive scroll, seems like everything works fine :/ |
Noticed the same a couple of days back - a temp fix would be to put a |
Cool workaround @vitass ! Not sure I understand how it works tho. |
Same Here, all my websites built with locomotive scroll complaining after Chrome update
By adding position:fixed works fine for now, but I'm not sure if it's a perfect way to resolve this issue |
@vitass Man, you are a life saver! 🙏 |
I am working on a client site built with locomotive then recently discovered this sad issue... and reported to Google already.
|
same problem, solved with |
I found that Chrome is repainting lots of elements during the scroll, maybe the problem is related to that. |
it seems like this issue is related to Paint Complexity by adding will force the browser to use hardware acceleration for paint and also works fine |
@Dushyant1295 Looks like for Chrome it's not enough for repainting. This fixed the issue on my side: .has-scroll-smooth {
position: fixed;
inset: 0;
} |
This one work perfectly for me! |
Why I am the only one :( |
I noticed that there was no screen recording of the issue, so here is an example of the problem, for clarity: Note in my case, adding the following fixes the issue whilst Google hopefully works on a solution: html.has-scroll-smooth {
backface-visibility: hidden;
transform: translateZ(0);
}
[data-load-container] {
position: fixed;
top: 0;
right: 0;
bottom: 0;
left: 0;
width: 100vw;
} |
Is there any new solutions? I am facing the same in Chrome |
@Artem-Semenov see #353 (comment).
|
In case someone still have an issue, you can do the trick by resizing the window
|
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:
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:
Report an issue
Desktop (please complete the following information):
Thank you 👊
The text was updated successfully, but these errors were encountered: