title: Difficulty accessing actual objects in "didInsertElement" code in Ember
body: <p>I'm having a repeated problem with accessing elements, specifically elements obtained via reference from another element, in Ember. I have javascript running in a "didInsertElement" hook in the view, which is what most places on the web seem to indicate is the correct place to be running that logic.</p>
  
  <p>However, the ember object I'm trying to access isn't real - Ember (presumably EmberData) is returning a blank placeholder object that doesn't have any of the required values. Every attribute is undefined.</p>
  
  <p>I've tried waiting for the promise to resolve... but it's not a promise, it's just a fake object with undefined attributes. I've tried using Ember.run.next, to insure things finished loading first. Neither of these two solutions, or any of the others I've tried, have worked.</p>
  
  <p>Here's an example of what I mean:
  template:</p>
  
  <pre><code>{{#each entry in list.entries}}
    {{display-note note=entry}}
  {{/each}}
  </code></pre>
  
  <p>component:</p>
  
  <pre><code>didInsertElement: function(){
    alert(this.get("note").get("title"));
  }
  </code></pre>
  
  <p>This inconsistently returns "undefined", even more inconsistently in situations where I'm passing a list of objects (something like <code>{{display-notes notes=list.entries}}</code> ).</p>
  
  <p>Doing things like <code>{{list.entry.title}}</code> in the template works fine, though - the data is loading, it's just that it's being replaced by a "fake object" until that happens, and I don't know how to tell the ember app to wait until it's real to run my code and try and access it.</p>
  
  <p>This is especially true for <em>self</em> references. Sometimes, rarely, the above code seems to work - but if I have a tree of, say, comments, which <code>hasMany</code> comments as <code>children</code>, attempting to access <code>children</code> fails even in the template. This might be due to another problem, though, or a combination of the two issues.</p>