-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Determinate progress-bar broken in @angular rc1 #430 [Still not working] #519
Comments
@Pixcell This works fine for me. Can you modify the Plunker, to represent your issue? |
@josephperrott I can reproduce this in my material2 sample app; we can take a look next time you're around |
@devversion, I tried a lot of things (even getting values from a webservice), but I can't reproduce the issue inside the plunker, sorry. I would really appreciate if you could keep me in the loop about this issue, and tell me what was the cause when you find it. Just let me know if I can help in anyway. |
Thanks a lot, it was fixed with release of alpha.5-2 ! |
* Currently if someone visits a link that contains a fragment that refers to an anchor element, the element won't be scrolled into view properly. This is because the `focusOnNavigation` calls `focus()` after the scroll into view. This causes the focused element to be visible in view. * Removes an unnecessary workaround for fixing fragment URLs. Fixes angular#396
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. |
Bug, feature request, or proposal:
Bug (#430)
I did everything like you said before closing the issue 430, but it is still not working (cf my last response)
I think you don't see comment notifications on closed issues, so I open a new one.
What is the expected behavior?
Progress bar to be filled with correct percentage
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Is there anything else we should know?
Working with Chrome Version 50.0.2661.94 (64-bit) on Mac OSX
Please tell me if you need anything else.
The text was updated successfully, but these errors were encountered: