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
In a reactive Form, when calling setValue(...) method of a formControl, the formControl should not be marked as not pristine.
A MdRadioGroup in a reactive form is marked as not pristine when setValue(...) is called on the control form.
View github https://github.com/feloy/ng2-master-detail
Angular 2.0.2 Material 2.0.0-alpha.9-3 OS Linux Browsers tested: Chrome 50, Firefox 46
The text was updated successfully, but these errors were encountered:
More details: Here is the comment @angular/forms describing that a form control should not be marked ditry when changed programmatically: https://github.com/angular/angular/blob/master/modules/%40angular/forms/src/model.ts#L180
I also see an error in the radio tests, where it is tested that the control should become dirty after being changed programmatically: https://github.com/angular/material2/blob/master/src/lib/radio/radio.spec.ts#L283
Sorry, something went wrong.
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.
kara
Successfully merging a pull request may close this issue.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
In a reactive Form, when calling setValue(...) method of a formControl, the formControl should not be marked as not pristine.
What is the current behavior?
A MdRadioGroup in a reactive form is marked as not pristine when setValue(...) is called on the control form.
What are the steps to reproduce?
View github https://github.com/feloy/ng2-master-detail
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Angular 2.0.2
Material 2.0.0-alpha.9-3
OS Linux
Browsers tested: Chrome 50, Firefox 46
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: