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
the align property from md-card-actions should be bindable.
console is throwing error, cannot use variable to assign value to align property.
https://plnkr.co/edit/qnEsY21BVoL2WCOFrTTu?p=preview
Not working as expected.
Angular 4.0.0, Material 2.0.0-beta.7, MACOSX, TypeScript 2.3.3
The text was updated successfully, but these errors were encountered:
fix(card): unable to bind to align attribute
eccc338
Fixes not being able to bind to the `align` attribute on the `md-card-actions`. Fixes angular#5490.
1bc33a4
Fixes not being able to bind to the `align` attribute on the `md-card-actions`. Fixes #5490.
fix(card): unable to bind to align attribute (#5495)
243b97d
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.
Sorry, something went wrong.
crisbeto
Successfully merging a pull request may close this issue.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
the align property from md-card-actions should be bindable.
What is the current behavior?
console is throwing error, cannot use variable to assign value to align property.
What are the steps to reproduce?
https://plnkr.co/edit/qnEsY21BVoL2WCOFrTTu?p=preview
What is the use-case or motivation for changing an existing behavior?
Not working as expected.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.0.0, Material 2.0.0-beta.7, MACOSX, TypeScript 2.3.3
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: