You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
[(ngModel)] without name is not allowed in a form. This used to work in the previous(now deprecated) forms. I think a mix for template and model driven form in the same template should be allowed. I see the following error when ngModel is used in a form without a associated control.
Name attribute must be set if ngModel is used within a form.
Example: <input [(ngModel)]="person.firstName" name="first">
Expected/desired behavior
[(ngModel)] should be allowed in a form without an associated control
What is the expected behavior?
[(ngModel)] should be allowed in a form without an associated control.
What is the motivation / use case for changing the behavior?
Allow mix of template and model driven form. This is specially useful in case part of the form in not really part of the actual business model.
Please tell us about your environment:
RC2 with new forms
Angular version: 2.0.0-rc.2
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
I'm submitting a ... (check one with "x")
Current behavior
[(ngModel)] without name is not allowed in a form. This used to work in the previous(now deprecated) forms. I think a mix for template and model driven form in the same template should be allowed. I see the following error when ngModel is used in a form without a associated control.
Name attribute must be set if ngModel is used within a form.
Example: <input [(ngModel)]="person.firstName" name="first">
Expected/desired behavior
[(ngModel)] should be allowed in a form without an associated control
Reproduction of the problem
You can see the error in the dev console of this plunker
https://plnkr.co/edit/CcXGHjI6jkkW8YpR28ZI?p=preview
What is the expected behavior?
[(ngModel)] should be allowed in a form without an associated control.
What is the motivation / use case for changing the behavior?
Allow mix of template and model driven form. This is specially useful in case part of the form in not really part of the actual business model.
Please tell us about your environment:
RC2 with new forms
The text was updated successfully, but these errors were encountered: