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

Progress Spinner initialization bug #8126

Closed
bOOm-X opened this issue Oct 30, 2017 · 2 comments · Fixed by #8139
Closed

Progress Spinner initialization bug #8126

bOOm-X opened this issue Oct 30, 2017 · 2 comments · Fixed by #8139
Assignees

Comments

@bOOm-X
Copy link

bOOm-X commented Oct 30, 2017

Bug, feature request, or proposal:

Bug

What is the expected behavior?

No "visual glitch" at the progress spinner initialization

What is the current behavior?

During a short period of time (1 second) the value attribute of the progress spinner is ignored and, the spinner start from almost "full" and go "back" to the correct initial value

What are the steps to reproduce?

https://plnkr.co/edit/vSTe3nqLuA1xiKSjzT1Z?p=preview

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

angular material 2.0.0-beta.12

Is there anything else we should know?

The issue appears only when angular flex-layout is imported (even if it is not used).

@crisbeto crisbeto self-assigned this Oct 30, 2017
@josephperrott josephperrott self-assigned this Oct 30, 2017
@josephperrott
Copy link
Member

It looks like this is caused because when the value is undefined, the stroke-dashoffset value becomes NaN which results in the css attribute not being applied. The css then animates from offset of 0 to whatever the new value is, which appears to animate as coming from 100%

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants