Two-way binding calls setter when property was updated from code about framework HOT 4 CLOSED

The calling of isChecked's setter the second time might be because of the way binding works here. I am thinking the following is the reason for the second call to setter.

dirty-checking -> find a change -> updates the view -> updates the property on view-model.

By design, if Aurelia doesn't update the value separately on view and view-model, the second call should never happen.

from framework.

Turns out, the call to activateCheckedState() is not updating the DOM. But dirty checking is doing the DOM updation. So if you somehow disable dirty checking, you would actually see the checkbox not being checked even if you click on the button until and unless dirty checking kicks off and finds there is change and updates the UI.

from framework.

@mhoyer this doesn't seem to be an issue in the latest release:
http://screencast.com/t/EV4ZPlQbUB

Can this be closed?

from framework.

Looks like it's working. Closing for now.

from framework.