<p dir="auto"><strong>I'm submitting a ...</strong></p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[x] bug report
[ ] feature request
[ ] support request"><pre class="notranslate"><code class="notranslate">[x] bug report
[ ] feature request
[ ] support request
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
When a route with a specified outlet has children, the activated child is put into the main router outlet, along side the route component that is already active inside this outlet, rather than in the named outlet.</p>
<p dir="auto"><strong>Expected/desired behavior</strong><br>
Routes whose (componentless) parents have a specified outlet, should go into said outlet.</p>
<p dir="auto"><strong>Reproduction of the problem</strong></p>
<p dir="auto">The relevant route:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="  {
    path: 'session',
    outlet: 'dialog',
    children: [
      {
        path: 'login',
        component: LoginComponent,
      },
      {
        path: 'register',
        component: RegisterComponent,
      }
    ]
  }"><pre class="notranslate"><code class="notranslate">  {
    path: 'session',
    outlet: 'dialog',
    children: [
      {
        path: 'login',
        component: LoginComponent,
      },
      {
        path: 'register',
        component: RegisterComponent,
      }
    ]
  }
</code></pre></div>
<p dir="auto">Plunkr reproducing the issue:<br>
<a href="http://plnkr.co/edit/W4t6c2hFWW3x9Sf2pn8S?p=preview" rel="nofollow">http://plnkr.co/edit/W4t6c2hFWW3x9Sf2pn8S?p=preview</a><br>
Click the three different links and you can see the login and register routes are put into the main outlet alongside the already activated home route, whereas the confirmation route is correctly placed in the named outlet.</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong><br>
I believe this to be a bug and the use case is demonstrated in the plunkr</p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.0-rc.5</li>
<li><strong>Browser:</strong> all</li>
<li><strong>Language:</strong> TypeScript 2.0.0</li>
</ul>
<p dir="auto"><strong>I'm submitting a ...</strong>  (check one with "x")</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[x ] bug report =&gt; search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question"><pre class="notranslate"><code class="notranslate">[x ] bug report =&gt; search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request =&gt; Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
Navigating to the <a href="https://angular.io/docs/ts/latest/cookbook/dynamic-component-loader.html" rel="nofollow">dynamic-component</a> documentation and trying to refer to the live example plunker at the <a href="https://angular.io/resources/live-examples/cb-dynamic-component-loader/ts/eplnkr.html" rel="nofollow">link</a> does not execute the code but throws errors</p>

<p dir="auto"><strong>Expected behavior</strong><br>
Example should be seen</p>

<p dir="auto"><strong>Minimal reproduction of the problem with instructions</strong></p>

<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong></p>

<p dir="auto"><strong>Please tell us about your environment:</strong></p>

<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.X</li>
</ul>

<ul dir="auto">
<li><strong>Browser:</strong> [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]</li>
</ul>

<ul dir="auto">
<li>
<p dir="auto"><strong>Language:</strong> [all | TypeScript X.X | ES6/7 | ES5]</p>
</li>
<li>
<p dir="auto"><strong>Node (for AoT issues):</strong> <code class="notranslate">node --version</code> = <strong>7.2</strong></p>
</li>
</ul>