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
I have a non-dynamic select field in my view with several options, and a number of ng-show conditions later on in the view that use the value of said select field to determine if they should display or not.
The ng-show blocks toggle when they're suppose to meaning the model is updating as expected but the select field rendering the model value doesn't. There's no special controller code changing the model, just the user interacting with the field.
alexkb
changed the title
select element not updating on user interactions, ngshow uses its model
bug: select element not updating on user interactions, ngshow uses its model
Jan 29, 2015
I've just updated my ionic project from v1.0.0-beta.13 to v1.0.0-beta.14, which also updated some of the angularJS dependencies (1.2.something to 1.3.6), and it seems to have fixed the issue.
I can't see anything obvious in the ionic changelog so perhaps it was an angular thing. Looking through angular's changelog, there are several mentions of select being improved between 1.2 and 1.3.6, so I'd say it was angular.
Type: bug
Platform: android 4.4 webview
I have a non-dynamic select field in my view with several options, and a number of ng-show conditions later on in the view that use the value of said select field to determine if they should display or not.
The ng-show blocks toggle when they're suppose to meaning the model is updating as expected but the select field rendering the model value doesn't. There's no special controller code changing the model, just the user interacting with the field.
The code looks something like this:
I can't replicate the issue in Chrome (via ionic serve), it only seems to be an issue after a mobile build for Android (and I haven't tried iOS yet).
Am I doing something wrong here or is this an ionic/angular bug?
The text was updated successfully, but these errors were encountered: