Lifecycle events are effectively fired twice

[FLamparski]

Events like activate-route-end are effectively fired twice. app-router dispatches them first on the route, then on itself; the events then propagate up all the way to window. Unless there is a substantial difference between the two events, dispatching the event just on the route should suffice.

[jmalonzo]

Do you have a simple test we can look into where these are triggered twice?

[FLamparski]

I'll try to come up with something, but so far I've noticed that this might be browser-specific (happens in Chrome, in Firefox the events don't seem to propagate up from the elements they've been dispatched on).