title: IE not calling lifecycle hooks or filling @Input until change detected?
body: <p>I'm using beta.0 because <a href="https://github.com/angular/angular/issues/6501" rel="nofollow">this outstanding bug</a> prevents angular 2 from working in IE in beta.1 and beta.2.</p>
  
  <p>Relevant code from SearchBar.ts</p>
  
  <pre><code>@Component({
    selector : 'search-bar',
    templateUrl: 'views/searchbar.html'
  })
  export class SearchBar {
    private history: SearchHistoryEntry[] = [];
  
    @Output() onHistory = new EventEmitter();
  
    constructor() {
      this.history = JSON.parse(localStorage.getItem('SearchHistory')) || [];
    }
  
    ngOnInit() {
      // The constructor doesn't have @Outputs initialized yet. Emit from this
      // life cycle hook instead to be sure they're received on the other side
      debugger;
      this.onHistory.emit(this.history);
    }
  }
  </code></pre>
  
  <p>Relevant code from home.html</p>
  
  <pre><code>&lt;search-bar (onHistory)="SearchBarHistory($event)"&gt;&lt;/search-bar&gt;
  </code></pre>
  
  <p>Relevant code from home.ts</p>
  
  <pre><code>SearchBarHistory(history: SearchHistoryEntry[]) {
    debugger;
    this.history = history;
  }
  </code></pre>
  
  <p>In Chrome this works just fine. The SearchBar's constructor correctly reads from <code>localStorage</code>, in <code>ngOnInit</code> it emits to my Home component who receives it, it's stored locally and the UI bindings tied to <code>history</code> update to show the information as it all should.</p>
  
  <p>In IE 11 this does not work. <code>ngOnInit</code> won't run until I click inside my search bar. It seems that any <code>@Input</code> or lifecycle hook (specifically I've tested <code>ngOnInit</code>, <code>ngAfterContentInit</code>, and <code>ngAfterViewInit</code> and they all behave the same) doesn't run until the component's change detection is triggered. If I refresh the page then it runs exactly like Chrome where no interaction is required for <code>@Input</code>s or lifecycle hooks to be called and my history goes through and gets bound like it should.</p>
  
  <p>I think this is a bug of the beta but in the mean time is there anything I can do to make it work the first time without an interaction or page refresh?</p>