md-tab error when using async pipe

[aminebizid]

Bug:

What is the expected behavior?

No console error

What is the current behavior?

zone.js:260 Uncaught TypeError: Cannot read property 'elementRef' of undefined

What are the steps to reproduce?

`
ngOnInit() {
this.weeks = this.inicidentReportService.getIncidentReports();
}

getIncidentReports() {
return this.http.get(
WebAPI.url() + '/api/incidentReport')
.map(request => request.json());
}

`

md-tab *ngFor="let w of weeks | async"

[snorkpete]

This behaviour happens even if the array used in the ngFor directive isn't directly using the async pipe, but instead is being passed from another component that used the async pipe.

For, for eg, we have SmartComponent described as above:

ngOnInit() {
this.weeks = this.inicidentReportService.getIncidentReports();
}

getIncidentReports() {
return this.http.get(
WebAPI.url() + '/api/incidentReport')
.map(request => request.json());
}

and the template:
<dumb-component [tabs]="weeks | async">

And it uses DumbComponent that actually has the tabs component, but accepts the array for the tabs as an input property:

@component({
selector: 'dumb-component',
template: `
......
md-tab *ngFor="let t of tabs"

....
`
})
DumbComponent{
@input() tabs;
}

DumbComponent will error out with the same errror

[RicardoVaranda]

@robertmesserle @jelbourn This doesn't seem to have fixed the issue, I'm still getting the error using:

"@angular2-material/core": "^2.0.0-alpha.6",
    "@angular2-material/input": "^2.0.0-alpha.6",
    "@angular2-material/tabs": "^2.0.0-alpha.6",
    "@angular2-material/toolbar": "^2.0.0-alpha.6",

[robertmesserle]

@RicardoVaranda Can you provide a plunker or some way for us to see your code failing? We include async tabs in our demo app, which is still working properly, so we'll need to see your app to determine what is different.

[RicardoVaranda]

It's been fixed, Update just required @angular/forms which was not met and caused the upgrade to fail and I missed it.

Thanks :)

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}