-
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
ChangeDetectionStrategy.OnPush problem #2663
Comments
Fixes the select's view not being updated when the value is set through a component that has its change detection set to `OnPush`. Fixes angular#2663. Fixes angular#2269.
Fixes the select's view not being updated when the value is set through a component that has its change detection set to `OnPush`. Fixes angular#2663. Fixes angular#2269.
I still see this bug in beta.2 when using reactive forms. |
I'm seeing the same, beta.2/angular 4.0.0 reactive forms with ChangeDetectionStrategy.OnPush still exhibits this behaviour. Is there a temporary quickfix? |
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
What is the expected behavior?
When using ChangeDetectionStrategy.OnPush the md-select value is cleared when ngModel variable is set to null
What is the current behavior?
ngModel is null but md-select value persists
What are the steps to reproduce?
https://plnkr.co/edit/RGEWSXblOySdltKBku9o?p=preview
What is the use-case or motivation for changing an existing behavior?
Application Performance Optimization
Which versions of Angular, Material, OS, browsers are affected?
Angular v2.4.3
Angular Material v2.0.0-beta.1
Is there anything else we should know?
Maybe there are other controls not working with ChangeDetectionStrategy.OnPush
The text was updated successfully, but these errors were encountered: