I am struggling with Angular framework to get my application run smoothly, but I can\'t resolve an issue with routing.
I have a top level AppComponent
and ap
We had encountered this bug when we were navigating somewhere in our solution.
In our sidebar component we use on-push change detection and we have had one this.ref.detectChanges()
when routing occured (change of parameters), which somehow broke routing (possibly kicking parallel running resolvers out of ngZone or something similar).
After changing this to the anyway preferred this.ref.markForCheck()
this bug didn't appear again.
I'm happy we didn't need a workaround, weird behavior though..
Hope this helps anyone having the same issue.