Regression using ngOptions asynchronously in angular 1.3

[FrenchDilettante]

Hi guys,

Just wanted to start by saying that Angular is a wonderful project and I'm having a great time working with it :)

I have an example of the issue in this jsFiddle: http://jsfiddle.net/88aw4yyq/

Consider this HTML:

<select name="test"
        ng-model="test"
        ng-options="opt.id as opt.label for opt in availableOptions">
</select>

And this controller:

$scope.test = '';
$scope.availableOptions = [];

$timeout(function () {
    $scope.availableOptions = [
        {id: '', label: 'Please select...'},
        {id: 1, label: 'opt1'},
        {id: 2, label: 'opt2'}
    ];
}, 1000);

The $timeout simulates any regular AJAX request. {id: '', label: 'Please select...'} is added for convenience for the user.

Expected behavior: 'Please select...' should be selected once the data is loaded.

Actual behavior: An empty option is added on top in the select field.

Angular versions: 1.3.0 this is a regression, 1.2.x was working fine.

Browser versions: Tested on Fx/Chrome (latest versions) on both OS X & Windows.

If anyone else is encountering the issue, here is a workaround:

$scope.test = '';
$scope.availableOptions = [
    {id: '', label: 'Please select...'}
];

$timeout(function () {
    $scope.availableOptions = $scope.availableOptions.concat([
        {id: 1, label: 'opt1'},
        {id: 2, label: 'opt2'}
    ]);
}, 1000);

[anotherchrisberry]

I just ran into this same issue (plunker here: http://plnkr.co/edit/NgPGrklA3ng6bmnPjxmw?p=preview) and ended up with the same solution (pre-filling the options holder with the known selected value). The workaround is kind of ugly but not terrible.

Tested in Firefox, Chrome and Safari but did not see the behavior in Firefox. Only tested on OS X.

This is a big problem for our group. All versions of AngularJS are okay up until the last 1.3.0 version. There's no simple workaround for us as every select box in our application is populated the same way and now none of them work as expected. I hope this bug gets fixed ASAP. Seems like it was introduced with 1.3.0. Now going back to using the RC release while waiting for someone to at least back out the change in the options that was made just prior to the 1.3.0 release :-(

[ajohnston256]

Can you assign this to me? I think I see the problem, and I'll try to get a pull request ready for tomorrow.