Activity

1. IgorMinar

   added a commit that references this issue on Sep 3, 2011

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

   This issue will close once commit 3a779a4 is merged into the 'master' branch.

   3a779a4
2. IgorMinar commented on Sep 3, 2011

   

   IgorMinar

   on Sep 3, 2011

   Contributor

   More actions

   thanks Kai for the nice test case. can we send you a t-shirt for this and other bug reports? email me your size, shirt preference, address and phone number.

   https://plus.google.com/104744871076396904202/posts/VuF67m5eQ2v
3. IgorMinar commented on Sep 3, 2011

   

   IgorMinar

   on Sep 3, 2011

   Contributor

   More actions

   the fiddle now works well with the latest build: http://jsfiddle.net/IgorMinar/AXLyY/1/
4. groner

   added 4 commits that reference this issue on Sep 5, 2011

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

   This issue will close once commit bf69aa1 is merged into the 'master' branch.

   bf69aa1

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

   This issue will close once commit dae4b97 is merged into the 'master' branch.

   dae4b97
5. groner commented on Sep 5, 2011

   

   groner

   on Sep 5, 2011

   ContributorAuthor

   More actions

   Pardon the spam. I was trying to figure out the right options to cherry pick this onto my v0.9.x+fixes branch.
6. IgorMinar

   closed this as completedin 0653441on Sep 8, 2011