![BUG: elements from previous route are still in the DOM when ngOnInit and ngAfterViewInit are executed · Issue #35879 · angular/angular · GitHub BUG: elements from previous route are still in the DOM when ngOnInit and ngAfterViewInit are executed · Issue #35879 · angular/angular · GitHub](https://user-images.githubusercontent.com/13590797/76027033-37f39280-5f30-11ea-9f31-d501d9c1b6df.png)
BUG: elements from previous route are still in the DOM when ngOnInit and ngAfterViewInit are executed · Issue #35879 · angular/angular · GitHub
![Angular Web Component routing reroutes to last component routed when we get back to the web component - Stack Overflow Angular Web Component routing reroutes to last component routed when we get back to the web component - Stack Overflow](https://i.stack.imgur.com/BgJYw.png)
Angular Web Component routing reroutes to last component routed when we get back to the web component - Stack Overflow
![angularjs - Old and New component data using route both are displayed on screen in angular 4 - Stack Overflow angularjs - Old and New component data using route both are displayed on screen in angular 4 - Stack Overflow](https://i.stack.imgur.com/c7zdp.png)
angularjs - Old and New component data using route both are displayed on screen in angular 4 - Stack Overflow
![Using "replaceUrl" In Order To Honor The Back-Button While Chaining Absolute Redirects In Angular 7.2.13 Using "replaceUrl" In Order To Honor The Back-Button While Chaining Absolute Redirects In Angular 7.2.13](https://bennadel-cdn.com/resources/uploads/2019/router-chained-redirects-replace-url-angular7.png)