Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

fix(ng:options): ng:change should be called after the new val is set #548

Closed
wants to merge 1 commit into from

Conversation

IgorMinar
Copy link
Contributor

Closes #547

@IgorMinar
Copy link
Contributor Author

landed as 0653441

@IgorMinar IgorMinar closed this Sep 8, 2011
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng:change combined with ng:options fires with the old value instead of the new value
2 participants