This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Unable to use ng-model-options on the same tag as ng-app when ng-app is on html tag #16535
Closed
1 of 3 tasks
Comments
Hi, thanks for the report. From which version did you upgrade to 1.6.10? |
15.11
Le sam. 21 avr. 2018 08:38, Martin Staffa <[email protected]> a
écrit :
… Hi, thanks for the report. From which version did you upgrade to 1.6.10?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16535 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AByQUE_bB57N4k6S3MTMGekVjz7Y8x4dks5tqyhWgaJpZM4TdhNM>
.
|
Marke it as a regression. I'm not sure we'll do another 1.6. release, though - maybe you'll have to upgrade to 1.7 straight. |
Ok, nous problème. I have found a workaround by moving the ngModelOptions
elsewhere
Le mar. 24 avr. 2018 09:50, Martin Staffa <[email protected]> a
écrit :
… Marke it as a regression. I'm not sure we'll do another 1.6. release,
though - maybe you'll have to upgrade to 1.7 straight.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16535 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AByQUM-H_hQ7ZiT-Ry9IaEjMVs6sUk6wks5try2kgaJpZM4TdhNM>
.
|
Just noticed that this only happens when ngApp is on the html tag - maybe that's because this is the top most tag in an html document. |
Narretz
added a commit
to Narretz/angular.js
that referenced
this issue
Jul 27, 2018
Narretz
added a commit
that referenced
this issue
Jul 27, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm submitting a ...
Current behavior:
When using ngModelOptions on the same tag as the ngApp, the value of defaultModelOptions gets set to undefined. This causes errors for every ngModel directive in the template.
The error seems to come from NgModelOptionsController $onInit where the parentOptions is undefined and the createChild method can't be executed.
Expected / new behavior:
There should not be an error when a ngModelOption is defined on the same tag as an ngApp.
Or, it should be present in the migration documentation.
Minimal reproduction of the problem with instructions:
https://plnkr.co/edit/jOmVWDvIFuOyOWB2
AngularJS version: 1.6.10
Browser: Chrome 65, probably in all browsers
Anything else:
The text was updated successfully, but these errors were encountered: