<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"><pre class="notranslate"><code class="notranslate">[x] bug report
</code></pre></div>
<p dir="auto"><strong>Current behavior</strong><br>
Change detections running outside of zones have no effect.</p>
<p dir="auto"><strong>Expected behavior</strong><br>
Either the change detection should succeed or an explicit error should be thrown.</p>
<p dir="auto"><strong>Minimal reproduction of the problem with instructions</strong></p>
<p dir="auto">Demo: <a href="http://plnkr.co/edit/wtB971qbdZivPSyTkpvj" rel="nofollow">http://plnkr.co/edit/wtB971qbdZivPSyTkpvj</a></p>
<ul dir="auto">
<li>Cause an event to occur outside of Zone.js</li>
<li>Attempts to effect changes resulting from that event in an Angular component</li>
<li>(note: this also happens when the change detection strategy on <code class="notranslate">OnPush</code>)</li>
</ul>
<p dir="auto"><strong>What is the motivation / use case for changing the behavior?</strong></p>
<p dir="auto">In general, any events that happen outside of Zones. My situation came about as a result of listening to <code class="notranslate">paused</code> / <code class="notranslate">play</code> events on a video element, which apparently Zone.js does not wrap properly or did not wrap in this situation. It could also easily happen if a first or third-party module initializes some routine when it is first imported on which events can be fired.</p>
<p dir="auto">This would have been substantially more difficult to debug if it happened deep in some such 3rd party dependency <g-emoji class="g-emoji" alias="stuck_out_tongue" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f61b.png">😛</g-emoji></p>
<p dir="auto"><strong>Please tell us about your environment:</strong></p>
<p dir="auto">Irrelevant. OSX Sierra, VS Code.</p>
<ul dir="auto">
<li><strong>Angular version:</strong> 2.0.2</li>
<li><strong>Browser:</strong> all</li>
<li><strong>Language:</strong> all</li>
</ul>
<p dir="auto">Hello!<br>
On directives I have detected the following problem:</p>
<p dir="auto">If you include <code class="notranslate">coreDirectives</code> and <code class="notranslate">NgFor</code> in the same component, the ng-for instruction will be executed two times.</p>
<p dir="auto">Example in this plunker: <a href="http://plnkr.co/edit/tFGJVjO3z78GEXCTKFh4?p=preview" rel="nofollow">http://plnkr.co/edit/tFGJVjO3z78GEXCTKFh4?p=preview</a></p>
<p dir="auto">I think the framework need report an error with this info or render only one time the ng-for...</p>
<p dir="auto">Thanks and sorry my bad english <g-emoji class="g-emoji" alias="smile" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f604.png">😄</g-emoji></p>