New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
beta.1 ngModel/ngModelChange not working on select element in FireFox 43.0.4 #6573
Comments
+1 |
Also in Firefox 45.0a2 (2016-01-22). Could be b44d36c. It removes a |
For 44.0 also doesn't work. Temporary I've fix it locally with:
Bug is actual for select. |
It doesn't even work in Chrome properly, if you automate your angular2 application with protractor. Something's fishy about these "input"-Events |
@Sabartius could be related to #6311 - just a wild guess. |
+1 |
1 similar comment
+1 |
Circling back around - I've confirmed that @DenisKolodin's workaround works. Thanks! |
Also not working also on Edge 25 |
IE11 also has this problem. |
this fix works with the current FF and IE versions: #7185 |
+1 |
Using the workaround @DenisKolodin, I also found out that if you use it in a http://plnkr.co/edit/g2tbjJMpOfRwz8ZhY3dj?p=preview When changing the type of Emilia from "FirstName" to something different, the type of Max also changes. This also happens when the type of Example is the same as the type of Max and you change the type of Example to something different ... EDIT: This only seems to be a displaying issue, as the value of the last entry in the model stays the correct one ... |
I actually make this work (tested in Chrome and Firefox). I need to be able to select department for my employee. This is sth I used:
and in my view it looks:
I also had a problem with recognizing numbers as numbers (JS has returned me strings) so I implemented:
selected object looks like this:
:) |
@theodorejb "easy" also is an indication that the community could jump in. If this fix is important enough someone could take a stab and implement this "easy" fix and create a pull request. |
@robwormald @naomiblack please put this task on radar of team as candidate for the hotlist: A2 Blocking |
1+ got the same problem on IE11, solved with workaround:
|
Regarding @DenisKolodin 's workaround also add a handler for keyup. i.e. (keyup)="doSomethingWith($event)" so catch keypress changes most likely up and down arrows when selecting options. (keyup instead of keydown in case you have any validation dependent on selected option) |
(keyup) is not a workaround, because |
This is an issue for me in firefox on beta-15, does anyone know of a workaround? |
@tchoulihan I use this one: #6573 (comment) |
@e-oz Thank you so much. of course the |
Having the same issue on Android 4.4.4 WebView. The ngModelChange handler never executes. |
Thank you very much! |
just notice this bug when trying to test my web app on Firefox. PS: I'm using Angular2 beta 15. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm seeing an issue in
beta.1
that appears to be a regression frombeta.0
.ngModel/ngModelChange
don't appear to work at all in Firefox, at least on selects. Here's a plunkr demo. You'll notice if you change the script src's to beta.0, the selects work as expected. Is there a breaking change that I'm missing? I don't see anything aboutngModel/ngModelChange
in the changelog.The text was updated successfully, but these errors were encountered: