Forum Replies Created
-
AuthorPosts
-
digiman1Member
Thanks for the response, Ryan.
I'm puzzled, though... since the HTML is actually parsed properly in post/page titles (i.e. <sup> in the post title displays a superscript on the single-post display), do you think the thinking is that the widget's output of the title is somehow more vulnerable to spurious actions?
I know it *used* to be that there was only a small subset of html tags that the widget actually parsed (I used to use <br/> and - which I presumed was for page-code cleanliness (like eliminating html from excerpts to make sure page flow was not interrupted) as well as seecurity. But now it looks like even that has been eliminated.
Separately, via help, I was just informed that the "development team is aware of this issue and will be releasing a fix soon", but no ETA or timeline yet. And in the meantime, I was pointed at the Genesis Sandbox Featured Content Widget, which reportedly *does* parse some HTML in widget-rendered post titles. (I haven't tried it yet, though.)
Anyway... I get what you're thinking. I'm going to poke around with the Sandbox version and see how that responds. I'll post back with an update. Thanks again!
Chris
-
AuthorPosts