-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
svgIcon with bound expression in contents fails for IE 11 #6093
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
isaacplmann
changed the title
svgIcon with bound expression in
svgIcon with bound expression in contents fails for IE 11
Jul 27, 2017
jelbourn
added
the
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
label
Jul 27, 2017
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 28, 2017
* Fixes an error that was being logged by IE11 for icons that are toggled via `ngIf` and have a binding expression. * Some minor readability improvements in the icon component. Fixes angular#6093.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 29, 2017
* Fixes an error that was being logged by IE11 for icons that are toggled via `ngIf` and have a binding expression. * Some minor readability improvements in the icon component. Fixes angular#6093.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Aug 1, 2017
* Fixes an error that was being logged by IE11 for icons that are toggled via `ngIf` and have a binding expression. * Some minor readability improvements in the icon component. Fixes angular#6093.
tinayuangao
pushed a commit
that referenced
this issue
Aug 2, 2017
* Fixes an error that was being logged by IE11 for icons that are toggled via `ngIf` and have a binding expression. * Some minor readability improvements in the icon component. Fixes #6093.
tinayuangao
pushed a commit
that referenced
this issue
Aug 2, 2017
* fix(icon): error when toggling icon with binding in IE11 * Fixes an error that was being logged by IE11 for icons that are toggled via `ngIf` and have a binding expression. * Some minor readability improvements in the icon component. Fixes #6093. * fix: address feedback
Thanks!
…On Aug 2, 2017 7:14 PM, "tinayuangao" ***@***.***> wrote:
Closed #6093 <#6093> via #6102
<#6102>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6093 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA0lQEKyTpKXwmeCbPhxkRjzHEUKSfKgks5sUQLzgaJpZM4OlqfX>
.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Bug, feature request, or proposal:
This fails in IE 11 if the
md-icon
component is hidden and shown. Removing{{myIcon}}
from the template avoids the error.What is the expected behavior?
No error is shown in the console. The icon is not duplicated.
What is the current behavior?
An error appears in the console and the icon is duplicated.
Error from the console
What are the steps to reproduce?
http://plnkr.co/edit/IxGqqudBSwWHompYGZtD?p=preview
What is the use-case or motivation for changing an existing behavior?
I wanted to fall back to having the name of the icon appear on the screen if the svg doesn't load over the network. This works great in other browsers, but fails for IE 11.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.3.1, Material 2.0.0-beta.8, IE 11
Is there anything else we should know?
The error happens in DefaultDomRenderer2:
Because you're setting innerHtml here as a workaround for this issue
...which runs straight into the situation discussed here. Namely, setting
innerHtml
on a parent node and then trying to update thenodeValue
of a removed node fails silently in modern browsers, but IE 11 throws an error.The text was updated successfully, but these errors were encountered: