Closed okni-c closed 2 years ago
I believe switching the ngAfterViewInit to ngOnContentInit should fix this: https://angular.io/api/core/AfterContentInit
I believe switching the ngAfterViewInit to ngOnContentInit should fix this: https://angular.io/api/core/AfterContentInit