You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Directives inside an ngRepeat fail to update properly when the data model being repeated changes. See here: http://plnkr.co/s87euU5fMWeGtdtv41Qo. Does not happen in <= 1.1.5
The text was updated successfully, but these errors were encountered:
I think the problem here is that ng-repeat is setting up the trackByIdFn to use trackByIdObjFn when it is supposed to be using trackByIdArrayFn. I think it is doing this because the first time the ngRepeatAction watch handler is called, the collection is undefined, which means that isArrayLike(collection) returns false.
…nitially undefined
Previously if the collection model was set to undefined on the first digest,
the repeater would get confused and not use the correct tracking function
for associating model with dom elements in the repeater.
Closesangular#4145Closesangular#3964
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
…nitially undefined
Previously if the collection model was set to undefined on the first digest,
the repeater would get confused and not use the correct tracking function
for associating model with dom elements in the repeater.
Closesangular#4145Closesangular#3964
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Directives inside an ngRepeat fail to update properly when the data model being repeated changes. See here: http://plnkr.co/s87euU5fMWeGtdtv41Qo. Does not happen in <= 1.1.5
The text was updated successfully, but these errors were encountered: