Hi Sander, thank you for your answer, but the '$' wasn't the problem, as the same behavior happened on other properties as well in other locations.
I decided to use "ngIf" now, as it makes sense anyway (I just didn't really know it existed previously) and it works fine. I'm still thinking that it might be an angular bug as changing: <!-- CHANGING: --> <div ng-show="someVar.something"></div> <!-- TO: --> <div ng-if="someVar.something"></div> was enough to make it disappear. I will keep my eyes open and try to recreate it in a fiddle. I'm still confused about it. Best, Johnny On Monday, October 6, 2014 7:09:27 AM UTC+2, Sander Elias wrote: > > Hi Jonathan, > > It’s difficult to say anything about this, without having a reproducible > example. While researching your bug, I found nothing that could explain > this. > If you have a a spot in your system where you can test this, can you try > testing it without a $ in the resource name? Meaning, replace > scope.someInstance.$resolved with something like > scope.someInstance._resolved. I have a gut feeling this might help. Its a > 70/30 change. So don’t > > get your hopes up too much. > > Regards > Sander > > -- You received this message because you are subscribed to the Google Groups "AngularJS" 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 http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
