We have an older application in production that is based off of angular 
v1.3.16 and has been chugging along just fine.
In a recent feature addition I attempted to update the angular version to 
1.4.0 (introduced a 3rd party service that I had THOUGHT was dependent on 
it).
Everything seemed fine after the update until I noticed an odd behavior 
with all of the select controls in the UI.
In 1.4 the selection worked fine on the first selection. However all 
subsequent selections were off by one index, and basically didn't recognize 
the last item in the array of selection objects in the collection and 
reported (in error) the wrong selected item (off by one index) in the 
interaction.

I rolled back the angular version and all is working fine again (thankfully 
my original thought that an upgrade was necessary was incorrect). But I'm 
curious on what might have happened here. Was there a bug in 1.4, or is it 
necessary to change the code to migrate from 1.3 -> 1.4 here?

thanks,
Karl

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to