Angular 2, DomSanitizer, bypassSecurityTrustHtml, SVG

I’ve been using DomSanitizer with some 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…

[tomgallagher]

Yes. Though not here.

Someone kindly answered the question on Stack Overflow

Cheers

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}