-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Uncaught promise error in 1.1.0 #255
Comments
Thanks for reporting. Let's see if this is related to #256 |
Will you please just catch it until you'll figure it out? its really hazardous.. |
No solution yet? |
Same problem here! |
Thanks for the fix. Here the command for installing from the commit:
|
Can you test the latest progressbar.js from latest master? I think this should work similarly as @dmarman commented before:
|
The root cause of the problem is that The solution is to make sure to |
FYI, I have incorporated @wparad's jeremyckahn/shifty#115 fix into the latest v.2.9.0 release. Thank you @wparad! |
Is there any timeframe for having this issue solved? |
Now I'm having the Is this repository abandoned? |
Just to get some clarity on the previous two comments, were they directed at @kimmobrunfeldt or myself? |
Mine was directed to progressbar.js so it's @kimmobrunfeldt |
As a temporary workaround, you can set option |
Catch "uncaught in promise"-error that is thrown when animate function is called while an animation is still running.
Hi,
Firstly, I want to thank you for your library, it adds a nice touch to our application.
As I am a developer, it's sometime nice when we know how our creation is used, so I've attached a partial screenshot to show to you our use case.
Secondly, I encouters a little issue since I've upgrade progressbar.js from 1.0.1 to 1.1.0.
In my browser console, there is sometime one or multiple uncaught promise errors:
It does'nt seem to affect the UI. Unfortunatly, I have not been able to find exactly why it occurs.
By by looking into the diffs from 1.0.1 to 1.1.0,
I have been able to find that the error may be caused since the upgrade of the
shifty
dependency from the Pull Request #196 (commit).By adding an empty catch function to R118-R121, the promise error is handled and it seem to not affect the UI. But, I'm not sure that it is the right way to fix this problem...
I hope it helps you, thank you very much!
The text was updated successfully, but these errors were encountered: