<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="[ ] bug report
[ X] 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">[ ] bug report
[ X] 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>
With multiple &lt;ng-content&gt;&lt;/ng-content&gt; only works last one.</p>
<p dir="auto"><strong>Expected/desired behavior</strong><br>
Both should paint content if condition met.</p>
<p dir="auto"><strong>Reproduction of the problem</strong></p>
<p dir="auto"><a href="http://stackoverflow.com/questions/38768324/angular2-rc-4-ng-content-duplicated-dont-work" rel="nofollow">http://stackoverflow.com/questions/38768324/angular2-rc-4-ng-content-duplicated-dont-work</a></p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&lt;div *ngIf=&quot;dialog&quot;&gt;
  &lt;ng-content&gt;&lt;/ng-content&gt;
&lt;/div&gt;

&lt;!-- for pages not in dialog popups put all div structure --&gt;
&lt;div *ngIf=&quot;!dialog&quot; class=&quot;container content&quot;&gt;
  &lt;div class=&quot;page-header&quot;&gt;
    &lt;h2&gt;{{title}}&lt;/h2&gt;
  &lt;/div&gt;
  &lt;div class=&quot;row&quot;&gt;
    &lt;div class=&quot;col-md-12&quot;&gt;
      &lt;ng-content&gt;&lt;/ng-content&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
"><pre class="notranslate"><code class="notranslate">&lt;div *ngIf="dialog"&gt;
  &lt;ng-content&gt;&lt;/ng-content&gt;
&lt;/div&gt;

&lt;!-- for pages not in dialog popups put all div structure --&gt;
&lt;div *ngIf="!dialog" class="container content"&gt;
  &lt;div class="page-header"&gt;
    &lt;h2&gt;{{title}}&lt;/h2&gt;
  &lt;/div&gt;
  &lt;div class="row"&gt;
    &lt;div class="col-md-12"&gt;
      &lt;ng-content&gt;&lt;/ng-content&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

</code></pre></div>
<p dir="auto"><strong>What is the expected behavior?</strong></p>
<p dir="auto">Both should paint content if condition met.</p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong></p>
<p dir="auto">Paint content in one or another container</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.4</li>
<li><strong>Browser:</strong> [all]</li>
<li><strong>Language:</strong> [ TypeScript ]</li>
</ul>
<p dir="auto">**I'm submitting a ...</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>
I'm using a guard to protect a route (<strong>View Two</strong>). User can go from <strong>View One</strong> to <strong>View Two</strong>. Guard checks if application has some state. If not, the guard redirect the user on a dedicated page (<strong>View State</strong>). On that page user will give the expected state to application. After that, I do a <strong>location.back()</strong>. This calls send back the user on page <strong>View One</strong> not on <strong>View Two</strong>.</p>
<p dir="auto"><strong>Expected behavior</strong><br>
I will like that 'location.back()' back to the cancelled route (<strong>View Two</strong>)</p>
<p dir="auto"><strong>Minimal reproduction of the problem with instructions</strong><br>
<a href="https://plnkr.co/edit/wxRFQlXNyClzLStcKtZQ?p=preview" rel="nofollow">A demonstration on plunkr</a></p>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong><br>
In my application, there are optional pages (optional functionalities). Those pages can be accessed only if some configurations has been done before. When users try to navigate to those pages for the first time, I redirect them to the configuration pages. On those configuration pages, I want to use 'location.back()' to back to the cancelled routes.</p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<ul dir="auto">
<li>
<p dir="auto"><strong>Environment:</strong> Windows 7, Atom, npm, Webpack-dev-server</p>
</li>
<li>
<p dir="auto"><strong>Angular version:</strong> 2.4.8</p>
</li>
<li>
<p dir="auto"><strong>Browser:</strong> all</p>
</li>
<li>
<p dir="auto"><strong>Language:</strong> TypeScript 2.1.5</p>
</li>
<li>
<p dir="auto"><strong>Node (for AoT issues):</strong> <code class="notranslate">node --version</code> = 6.9.5</p>
</li>
</ul>