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
A collection that contains an undefined entry that is later replaced with a real Em.Object instance can leave chains stuck in the pendingQueue. Specifically, when the observed objects in question contain nested properties such as:
When nested properties ('foo.bar') are used in a view template, chains get stuck. When only top-level properties ('baz') are used, nothing gets stuck. May be related to Issue 405.
@robharper I just reviewed this again and it looks like it works fine. #405 is closed now, so I'm going to assume this is ok. If I'm mistaken, please provide more detailed information including OS and browser and exactly what results I should be seeing. Thanks.
A collection that contains an undefined entry that is later replaced with a real Em.Object instance can leave chains stuck in the pendingQueue. Specifically, when the observed objects in question contain nested properties such as:
When nested properties ('foo.bar') are used in a view template, chains get stuck. When only top-level properties ('baz') are used, nothing gets stuck. May be related to Issue 405.
I've created a jsfiddle that shows chains stuck indefinitely: http://jsfiddle.net/rharper/Fcb4m/
The text was updated successfully, but these errors were encountered: