-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
Toggle and checkboxes report incorrect value through ng-change. #1349
Comments
Hello guys, it seems that the issue is still present with ion-toggle: with ion-toggle the ng-change callback has the old value in the scope whereas the ion-checkbox has the correct behaviour |
👍 it does indeed appear that in 1.0.0-beta.8 I am ugly-hacking-ly getting around it by wrapping the inside of my change handler in a $timeout; it will be nice to have the fix in the next release. |
Looking at this again asap. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
<ion-toggle>
and<ion-checkbox>
elements incorrectly report their state when state is accessed through$scope
in anng-change
callback. It appears that they're returning their pre-transition state.This behavior can be seen in action here: http://plnkr.co/edit/ImILoeeGWHQ2Zpw9uWkl?p=preview
Values seen in
ng-click
callbacks are correct.The text was updated successfully, but these errors were encountered: