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 has been archived by the owner on Apr 12, 2024. It is now read-only.
I think the fix is to either A) fix select.js to treat null as an empty value or B) fix #2249 to return undefined if the entire expression chain cannot be evaluated.
I think A is best, since null is not a real value anyway (not the kind of value you could be selecting from a select box).
The text was updated successfully, but these errors were encountered:
If I have an empty option in SELECT with:
Then ng-model correctly picks the empty variable. However, if the object is null, then the empty option is not picked:
I traced this down to https://github.com/angular/angular.js/blob/master/src/ng/directive/select.js#L256 -- it checks for undefined ONLY, but in the 2nd case, $scope.$eval("obj.item") comes back as null due to #2249.
Demo:
http://plnkr.co/edit/RbPnV3d3LHhkyCoiTsGo?p=info
I think the fix is to either A) fix select.js to treat null as an empty value or B) fix #2249 to return undefined if the entire expression chain cannot be evaluated.
I think A is best, since null is not a real value anyway (not the kind of value you could be selecting from a select box).
The text was updated successfully, but these errors were encountered: