I've been using DomSanitizer with an SVG in an html string.
Previous to the current version of Angular, this worked just fine:
this.domSanitizer.bypassSecurityTrustHtml(content);
Now I am getting an object back called
SafeHtmlImpl {changingThisBreaksApplicationSecurity: "<svg> blah </svg>"}
changingThisBreaksApplicationSecurity
Is there now a new way to access the output of the DomSanitizer? Should I be receiving it as SafeHTML type or something? What's the point in having bypassSecurityTrustHtml if it still filters html?
Any answers on a postcard? Please...
DEMO : https://plnkr.co/edit/Qke2jktna55h40ubUl8o?p=preview
Use
DomSanitizer.bypassSecurityTrustHtml
:More information: https://angular.io/docs/ts/latest/guide/security.html#bypass-security-apis