Angular - Lifecycle Hooks
Why is
ngAfterViewInit preferred over ngOnInit for DOM manipulation in Angular components?Why is ngAfterViewInit preferred over ngOnInit for DOM manipulation in Angular components?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Compare ngOnInit and ngAfterViewInit timing
ngOnInit runs before the view is fully rendered, so DOM elements may not exist yet.Step 2: Understand why DOM manipulation needs view ready
ngAfterViewInit runs after the view and child views are initialized, ensuring DOM elements are accessible.Final Answer:
Because the component's view and child views are fully initialized only after ngAfterViewInit runs -> Option BQuick Check:
DOM manipulation requires view ready after ngAfterViewInit [OK]
Quick Trick: Manipulate DOM only after ngAfterViewInit runs [OK]
Common Mistakes:
- Thinking ngOnInit runs multiple times
- Believing ngAfterViewInit runs before creation
- Assuming ngOnInit cannot access properties
Master "Lifecycle Hooks" in Angular
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Angular Quizzes