md-spinner and md-progress-circle indeterminate are blinking #926
Labels
P2
The issue is important to a large percentage of users, with a workaround
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 28, 2016
Fixes the progress circle animation not working, because the calculations weren't correct. When 14c1765 was introduced, one of the values uses the time since epoch, whereas the other one is the time since the page was opened. Fixes angular#926.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 28, 2016
Fixes the progress circle animation not working, because the calculations weren't correct. When 14c1765 was introduced, one of the values uses the time since epoch, whereas the other one is the time since the page was opened. Fixes angular#926.
|
Wow, that's pretty glaring. How did we not see this... |
jelbourn
added
P2
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
The spinner is supposed to have a smooth animation.
What is the current behavior?
Using the most recent commit, the progress spinner is blinking.
What are the steps to reproduce?
See the demo app:
https://material2-test.firebaseapp.com/progress-circle
Pull from the latest commit, and put a spinner/indeterminate circle into your app:
<md-progress-circle mode="indeterminate"></md-progress-circle>or
<md-spinner></md-spinner>What is the use-case or motivation for changing an existing behavior?
Fix the issue before it gets deployed.
Which versions of Angular, Material, OS, browsers are affected?
AngularJs 2: 2.0.0-rc.4
Angular 2 Material: Current version from git
Is there anything else we should know?
The progress-circle is working normally for version 2.0.0-alpha.6-2 so not exactly sure what is causing it right now. In fact, I'm not even sure if this is just a weird bug that'll get fixed with the next deployment but I just thought that you guys should know that it's happening.
Thanks!
The text was updated successfully, but these errors were encountered: