Skip to content
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

Low scrolling performance in Safari #53

Closed
NikSimonov opened this issue Jul 13, 2018 · 6 comments
Closed

Low scrolling performance in Safari #53

NikSimonov opened this issue Jul 13, 2018 · 6 comments

Comments

@NikSimonov
Copy link

I have issues with scrolling performance in Safari, using latest version without jquery. Can you give me any optimization advice?

@KingSora
Copy link
Owner

KingSora commented Jul 13, 2018

Yes, please answer me some questions first:

  • On which element are you using the plugin and with which options are you initializing it?
  • Which OS version and which Safari version are you using?
  • If you are using a different browser, is the performance the same as in Safari?
  • On how many elements are you initializing the plugin?
  • Can you perhaps provide the link to your page so I can check what might cause the issue?
  • Is the scroll-performance on the documentation page also "low"?

@NikSimonov
Copy link
Author

  • using it on body, options are { autoUpdate: true, sizeAutoCapable: false }
  • OS 10.13.5, Safari 11.1.1
  • works perfectly fine in Chrome and Firefox
  • just the body
  • sorry, but i can't, maybe I'll look into any specific elements, that can cause problems?
  • performance is fine on the documentation page

@NikSimonov
Copy link
Author

Okay, nevermind, figured it out. Page has many placeholder images with filter: brightness(0) contrast(0);

@KingSora
Copy link
Owner

Is there any particular reason why you've set the autoUpdate to true?
Please initialize the plugin with autoUpdate : null (thats the default value). This should increase the performance.

@NikSimonov
Copy link
Author

#23
It was your question "Does the option autoUpdate : true improve the performance?"
I thought, if you asked about it, so there is a way it can improve it, that's it.
Reverting to default. Thanks for helping out.

@KingSora
Copy link
Owner

KingSora commented Jul 13, 2018

Now I understand.
Genereally autoUpdate : null will give you the best performance for your browser. Only in some very special cases (like many animations or very many elements) you want to
use a updade-loop with autoUpdate : true because the updates will happen on a frequent basis. - But even in this cases a performance gain isn't very likely, but nevertheless I wanted to mention this possibility in the previous issue.

I'm glad I could help you, if you have other questions or problems, please don't hesitate to open a issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants