Parsing URL as markup
HardwareGeek last edited by
Continuing the discussion from Status: I'm Doing Science and I'm still alive.:
Post contained the following link in raw:
<a target="_blank" href="https://en.m.wikipedia.org/wiki/Pao_v._Kleiner_Perkins">FTFY.</a>
In the baked version, the link URL is transformed to this:
Discourse parsed the
_characters in the URL as markup, transformed them to (mismatched)
</em>tags, and totally Belgiumed-up the link. (I'm not sure whether Discourse URL-encoded the
>characters, or the browser did. In either case, it's a secondary effect; it wouldn't have happened if Discourse hadn't already buggered the URL.)
hungrier last edited by
Could you even make a parser this dysfunctional on purpose?
NedFodder last edited by
That's the next OMGWTF contest.
Ah yes, but it doesn't allow me to set a
Does Discourse allow that? I know it didn't allow rel="nofollow" last time I tried it.
riking last edited by
That's been added to the whitelist, but I don't think I have the stomach to figure out this parser bug... just use your "open external links in new tab" setting.
Zecc last edited by