Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

ngChange not always fired on select #10382

Closed
stejanse opened this issue Dec 9, 2014 · 2 comments
Closed

ngChange not always fired on select #10382

stejanse opened this issue Dec 9, 2014 · 2 comments

Comments

@stejanse
Copy link

stejanse commented Dec 9, 2014

Using ngChange on a selectbox is not working properly when selecting options bij pressing keys. The second ngChange event that should be fired never happens. For reproducing I created a Plunker:

http://plnkr.co/edit/fHT7TtClLcoEHlQr75fr?p=preview

Steps to reproduce:

  1. Focus on the selectbox, but don't have it opened.
  2. The counter next to the selectbox counts the number of ngChange events.
  3. Press 'O' once, counter increases to 1.
  4. Press 'O' twice, counter does not increase.
  5. Now press 'O' a number of times, the ngChange event works perfectly.

As far as I know the bug occurs in all browsers and at least in version 1.2.26, 1.3.2, 1.3.4 and 1.3.6.

@gkalpak
Copy link
Member

gkalpak commented Dec 9, 2014

This is a duplicate of #9134 (and a few other issues) and only happens when there is no default empty option specified.

It is a Chrome bug (and has been reported here).

@pkozlowski-opensource
Copy link
Member

OK, let's close this as a duplicate of #9134.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants