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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
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:
jbedard
added a commit
to jbedard/angular.js
that referenced
this issue
Dec 22, 2018
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: