Childrouting inside auxiliary outlet works only in very specific cases #26672
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x ] Bug report
[ ] Performance issue
[ ] 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
[ ] Other... Please describe:
Current behavior
Routing inside auxiliary routes is broken.
Expected behavior
Same routing experience as inside primary routers. There should be no difference between routing inside primary router, auxiliary or nested routes. Each child route should be should behave consistently whatever parent outlet is.
Minimal reproduction of the problem with instructions
Angular 6.1.10
https://stackblitz.com/edit/angular-routing-default-aux?embed=1&file=src/app/app.routing.module.ts
Angular 7.0.0
https://stackblitz.com/edit/angular-routing-default-aux-a7?embed=1&file=src/app/app.routing.module.ts
Click on navigation links
What is the motivation / use case for changing the behavior?
Consistency in behavior of routing will prevent unexpected outputs.
Environment
Angular version: 6.1.10, 7.0.0
Browser:
- [ x] Chrome (desktop) version 69.0.3497.81 OS: Win7
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: XX
- Platform:
Others: