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
Closed

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

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
fix(ng:options): ng:change should be called after the new val is set
3a779a4 
Closes angular#547
@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
fix(ng:options): ng:change should be called after the new val is set
bf69aa1 
Closes angular#547

Conflicts:

	test/widgetsSpec.js
groner pushed a commit to groner/angular.js that referenced this issue Sep 5, 2011
@IgorMinar @groner
fix(ng:options): ng:change should be called after the new val is set
dae4b97 
Closes angular#547
@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.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(ng:options): ng:change should be called after the new val is set IgorMinar/angular.js
2 participants
@groner @IgorMinar