We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bug
When clicking on a button that will immediately become disabled, the ripple should remain until it fades out.
The ripple is immediately destroyed when the button state changes to disabled.
http://plnkr.co/edit/otcf7ejUS9GTY1s3s3v2?p=preview
Happy to open a PR if this is desired behavior
The text was updated successfully, but these errors were encountered:
Yep. We should remove the *ngIf and just use the mdRippleDisabled binding.
*ngIf
mdRippleDisabled
Let me know if you want to put a PR together. Otherwise I can take care of it :)
Sorry, something went wrong.
@devversion up at #4372!
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.
devversion
Successfully merging a pull request may close this issue.
Bug, feature request, or proposal:
Bug
Expected behavior
When clicking on a button that will immediately become disabled, the ripple should remain until it fades out.
Current behavior
The ripple is immediately destroyed when the button state changes to disabled.
What are the steps to reproduce?
http://plnkr.co/edit/otcf7ejUS9GTY1s3s3v2?p=preview
Is there anything else we should know?
Happy to open a PR if this is desired behavior
The text was updated successfully, but these errors were encountered: