<p dir="auto">Certain svg attributes are camelcased, such as <code class="notranslate">viewBox</code>. However, <code class="notranslate">[viewBox]</code> would be recognized by browsers as <code class="notranslate">[viewbox]</code> since it is not a standard SVG attribute, and so the important camelcasing information is lost.</p>
<p dir="auto">There should be a convention in Angular 2 for supporting bindings to SVG attributes.</p>
<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"><em>Note: Related to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="196970379" data-permission-text="Title is private" data-url="https://github.com/angular/angular/issues/13614" data-hovercard-type="issue" data-hovercard-url="/angular/angular/issues/13614/hovercard" href="https://github.com/angular/angular/issues/13614">#13614</a> and <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="199742976" data-permission-text="Title is private" data-url="https://github.com/angular/angular/issues/13853" data-hovercard-type="issue" data-hovercard-url="/angular/angular/issues/13853/hovercard" href="https://github.com/angular/angular/issues/13853">#13853</a></em><br>
Although arguably a duplicate, I filed this separate because it could be easily fixed by changing the signature to unblock unit tests separate from the underlying issue.  Also, I believe this shows that the unifying issue is ES6 implementation.</p>
<p dir="auto"><strong>Current behavior</strong><br>
ES6 distributions will result in certain syntax of anonymous functions to not have a prototype.  The JIT compiler <a href="https://github.com/angular/angular/blob/126fda2613b1ad87ff62591bb1d3a23cd8f369a1/modules/%40angular/compiler/src/jit/compiler.ts#L125">here</a> uses a signature for useFactory that fails all unit tests <a href="https://github.com/angular/angular/blob/8b81bb1eb6b57afce4c384f7db2e734cab06421e/modules/%40angular/core/src/reflection/reflection_capabilities.ts#L249">here</a>.</p>
<p dir="auto"><strong>Expected behavior</strong><br>
First, to unblock ES6 unit tests.  Second, to handle factories without prototypes.</p>
<p dir="auto"><strong>Minimal reproduction of the problem with instructions</strong><br>
Plunk <a href="https://plnkr.co/edit/R78PQPY5MMMSUv5hWYPM?p=preview" rel="nofollow">here</a><br>
Shows failure in es6.  Change everything to es5 distributions and it works.</p>
<ul dir="auto">
<li>
<p dir="auto"><strong>Angular version:</strong> 4.0.0-rc.1</p>
</li>
<li>
<p dir="auto"><strong>Browser:</strong> [Chrome@latest, edge]</p>
</li>
<li>
<p dir="auto"><strong>Language:</strong> [ES6]</p>
</li>
</ul>