router-outlet does not send activate event on attach

[Mysame]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

https://github.com/angular/angular/blob/5.0.1/packages/router/src/directives/router_outlet.ts#L66
In case an existing component gets mounted to a router-outlet, attach gets called.
Attach does not emit a change to the activateEvents EventEmitter, even though it does change the isActive property of the router.

Expected behavior

Attach also emits a change to the activateEvents EventEmitter

What is the motivation / use case for changing the behavior?

In my use case, I want my parent to attach events to the child components.
The children are loaded in a router-outlet, which resorts to me having to listen to router-outlet activate event in order to bind to the child components (for reasons, I can't use a service).

Environment

Angular version: 5.0.1

Browser:
- [x] All

[jasonaden]

I'm sorry but reported issues require a reproduction of the issue. We suggest using StackBlitz, Plunker or Github.

If this issue persists, please create a reproduction using one of the links above. Describe the difference between the expected and current behavior in a new issue with the reproduction linked.

[JihedHalimi]

We also have the same problem. To reproduce the issue, change the RouteReuseStrategy to reuse components. The activate event of the router-outlet is triggered when the component is created the first time but when we navigate away and then come back, the component is reused and the activate event is not triggered.

[jasonaden]

Sorry, this should have been closed back when the Need repo label was applied. There is still no reproduction attached, so I'll close now. If there's an issue with reproduction, please create a new issue.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}