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

optimize svg loading "especially for chrome" #47

Closed
ctf0 opened this issue Dec 11, 2017 · 6 comments
Closed

optimize svg loading "especially for chrome" #47

ctf0 opened this issue Dec 11, 2017 · 6 comments

Comments

@ctf0
Copy link

ctf0 commented Dec 11, 2017

chrome is very dump when it comes to svg, as having more than 15 or 20 svg on the same page could simply render a very unpleasant experience.

so as the package atm uses svg + blurring , masking, loop the numbers list at least a couple of times b4 showing the final value, it means that any other animation that happens at the same time will hang a bit.

so we need to find a way to optimize the svg animation to minimize the jerking effect that affects chrome, some solutions could be

@coderitual
Copy link
Owner

Thanks for your feedback and suggestions! I will be investigating possible options to make it more performant at certain circumstances.

@ctf0
Copy link
Author

ctf0 commented Dec 12, 2017

@coderitual btw, do you have any time frame for the new api ?

@coderitual
Copy link
Owner

I will be starting by the end of the week. Unfortunately December is quite busy for me so I would expect begining of Jan to have it ready. Ofc POC will be much faster. Also because this is an api change, all that will be part of v2. When do you need this?

@ctf0
Copy link
Author

ctf0 commented Dec 12, 2017

i wanted to use it in my prev mentioned package.
still np take ur time, but for a start can we get around the long list loop ?

@coderitual
Copy link
Owner

Yup, I can start from it.

@ctf0 ctf0 closed this as completed Mar 16, 2018
@coderitual
Copy link
Owner

I reopen as this is part of the future optimization. Sorry I didn't improve it yet. I would leave this though to keep this in mind. Performance especially on mobiles is not satisfying.

This issue was closed.
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