Angular ng-select bug in Chrome when using tab navigation and no default empty option

[vilmosioo]

There seems to be a weird bug when selecting values in Chrome on Windows using the keyboard only.

function MyCtrl($scope) {
    $scope.d = '';
    $scope.options = [1,2,3];
    $scope.d2 = '';
    $scope.options2 = [1,2,3];
}

<input><br>
<select ng-options="d for d in options" ng-model="d"></select><br>
<select ng-options="d for d in options2" ng-model="d2"></select><br>
<input>

JSFiddle:
http://jsfiddle.net/DrTCZ/4/

Steps to replicate:

1. Click on first text field
2. Press tab
3. Using the keyboard, select 2
4. Press tab
5. Using the keyboard, select 2

Notice the value of the first dropdown.

Any help would be appreciated!

[iox]

I have encountered the same issue. Somehow with Chrome, when using the keyboard in a select it fails the second time. This is a simplified JSFiddle showing the same problem: http://jsfiddle.net/UJkLX/

Reproduced both in Windows Chrome and in Linux Chrome

[tbosch]

Just tried a fiddle with static selects and it works fine: http://jsfiddle.net/guzGG/2/

So this is a valid bug!

[akanieski]

• 1

Noticed this too with Chrome.

[howlettt]

+1 We're seeing this as well

[callmekatootie]

Such issues have started cropping up in SO, so mentioning an alternative here in case someone is looking for it - have an option with an empty / null value within the select such as <option value="">Select One</option> and it will work: http://jsfiddle.net/JqnMr/

[yr12345678]

Thanks callmekatootie, that worked for me. Weird bug.

[camilleriluke]

Tested it on OSX Chrome Version 36.0.1985.143 and could not reproduce. Can someone please verify that this behaviour is still present?

[iox]

Reproduced in Ubuntu 12.04 with Chromium 36.0.1985.125 and Google Chrome 36.0.1985.125. I used this fiddle to check: http://jsfiddle.net/UJkLX/

[vilmosioo]

Cannot reproduce on OSX Chrome 36 anymore.

[gkalpak]

Still reproducible with version 1.3.0.-rc.2 on Chrome 37 (Window 8.1).

It might be related to #9134 and only happens when the is no default empty option specified.
If you define an empty option the problem disappears (demo here).

If that is indeed the case, it seems to be a Chrome bug (it's been reported here).

[bernhard-hofmann]

+1, reproduced in Chrome Version 39.0.2171.2 dev-m on Windows.

[bernhard-hofmann]

FWIW, this is a bug in Chrome (IMO) not in Angular. Chrome does not notify Javascript of the selection change. See this jsBin which logs changes to the console: http://jsbin.com/wofejo/1/

[lborgav]

I had the same issue using Chrome on Windows. Any solution?

[david0603]

Any eta for this? Thanks.

[vilmosioo]

This is not an angular bug but a Chrome bug.

[risingfish]

I believe this is related to this bug: https://code.google.com/p/chromium/issues/detail?id=415505

[Narretz]

Fixed in chrome 47: https://bugs.chromium.org/p/chromium/issues/detail?id=415505