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

ng:change combined with ng:options fires with the old value instead of the new value #547

Closed
groner opened this issue Sep 2, 2011 · 3 comments

Comments

@groner
Copy link
Contributor

groner commented Sep 2, 2011

See http://jsfiddle.net/gronky/AXLyY/

IgorMinar added a commit to IgorMinar/angular.js that referenced this issue Sep 3, 2011
@IgorMinar
Copy link
Contributor

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

@IgorMinar
Copy link
Contributor

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

groner added a commit to groner/angular.js that referenced this issue Sep 5, 2011
groner pushed a commit to groner/angular.js that referenced this issue Sep 5, 2011
@groner
Copy link
Contributor Author

groner commented Sep 5, 2011

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants