What is the correct way to make an unsafe bind to an attribute? In my case, I get undesired HTML entities in the title-attribute:
<a href="..." title="Something "goes bad"">Link</a>
(Angular 1.1.5)
-
be more specific about source of title and problem as it is nowcharlietfl– charlietfl2013-11-01 11:51:25 +00:00Commented Nov 1, 2013 at 11:51
-
I think my question is clear enough. I need to force the same behavior as the directive ng-bind-html-unsafe has, only for an attribute.Liglo App– Liglo App2013-11-03 11:21:27 +00:00Commented Nov 3, 2013 at 11:21
-
no you haven't....it displays properly in browser. Can think you've been clear enough with one sentence question that so far hasn't made sense...but won't get a lot of help around here without defining issues in detailcharlietfl– charlietfl2013-11-03 14:08:11 +00:00Commented Nov 3, 2013 at 14:08
Add a comment
|
1 Answer
" is how " is escaped in HTML (and XML) attributes, there's no way around it. It will display correctly on the page, however. Attribute contents aren't parsed as HTML so there's no need for an equivalent to bind-html-unsafe.
2 Comments
Liglo App
It's wrong, in the database stands: """, after the Output it should be "", but it is still a ". It is due to Angular's $sanitize Service.
Liglo App
Or, if they are not parsed as HTML, we maybe need a way to display " there, and maybe this question has just nothing to do with Angular?..