Ion-toggle (ionChange) triggered

This has been a fairly persistent and stubborn bug dating all the way back to v2 beta. The first thing that jumps out at me is the two-way model binding. If you take that out, specifically in the box direction (from controller to template), does anything change? I realize that’s not really necessarily a viable workaround because it eliminates what may be crucial functionality, but it may at least help narrow down the issue.

Another tactic you can use to work around this class of problem is to put guards around crazyEvent so that it ignores anything where the template and controller are already in sync, a la @jasonwaters’s suggestion in here.

1 Like