For some reason my @ViewChild in my Angular 5 App does not work. I have defined it like this in my component:
case-detail.component.html:
<div class="inner-tab-content" #innerTabContent>
<!-- // more content here -->
</div>
I have implemented @ViewChild
in my controller (above the constructor) like this:
case-detail.component.ts
@ViewChild('innerTabContent') tabContentElement: ElementRef;
And I want to access it here in the component: case-detail.component.ts
ngAfterViewInit() {
console.log("scroll top: " + this.tabContentElement.nativeElement);
}
I've implemented the AfterViewInit
interface. ngAfterViewInit() is called correctly. However, this.tabContentElement
is always undefined
.
Any help is greatly appreciated :)
ViewChild()
works fine on latest plunker Angular version with the scenario you describe.
Demonstration in this plunker : https://plnkr.co
/edit/KzWnkE5Hvp7NUow6YAxy
EDIT: Here is a replacement StackBlitz for the above Plunker: https://stackblitz.com/edit/angular-ivy-pzaglm
component :
ngAfterViewInit() {
console.log(this.testView); // correctly outputs the element in console, not undefined
}
Check that ElementRef and ViewChild are correctly imported from '@angular/core'
Your element might simply not be there at the time of AfterViewInit (in case there is a *ngIf
, for instance. (seems the case as per your comments)
In the latter case, you can use a wrapper element and ViewChildren
, that emits some event when a new child element is added - more info on documentation here : https://angular.io/api/core/ViewChildren
note that there might be some issue with native div
as per this question : @ViewChildren does not get updated with dynamically added DOM elements , but this can be worked around by using a new component that wraps your div, for instance.
Or you can also use a timeout to wait for the component to be rendered. I must say that I find this solution 'dirty', but glad it works for you :)