This repository has been 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.5k
ng-prop-* not working with "undefined" value #16797
Comments
jbedard
added a commit
to jbedard/angular.js
that referenced
this issue
Dec 22, 2018
Thanks for the bug report @vargarobert! That's definitely an issue, see #16798 which should get merged before 1.7.6 |
jbedard
added a commit
to jbedard/angular.js
that referenced
this issue
Jan 10, 2019
jbedard
added a commit
to jbedard/angular.js
that referenced
this issue
Jan 11, 2019
jbedard
added a commit
that referenced
this issue
Jan 11, 2019
jbedard
added a commit
that referenced
this issue
Jan 11, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm submitting a ...
Current behavior:
"Undefined" is ignored when passed down through a ng-prop-* directive.
Let's take an example:
<my-component ng-prop-text="$ctrl.text"></my-component>
this.text = 'abc'
...text is set as abc and later on
this.text = undefined;
the value of the text in my-component remains unchanged to abc
Expected / new behavior:
The value of text should be cleared in the above example (ofc you could clear with empty string but that's not the point)
ng-prop-* should accept any JS type.
AngularJS version: 1.7.5
and snapshot 1.7.6
Browser: [all]
The text was updated successfully, but these errors were encountered: