<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr - wizard04</title>
<link>http://snipplr.com/users/wizard04/tags/markup</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Thu, 23 May 2013 12:03:40 GMT</pubDate>
<item>
<title>(Other) --Snipplr-- Workaround: Code in Comments</title>
<link>http://snipplr.com/view/22799/snipplr-workaround-code-in-comments/</link>
<description><![CDATA[ <p>For some reason, Snipplr has decided not to HTML-encode &amp;lt; and &amp;gt; signs (i.e., replacing them with `&amp;lt;` and `&amp;gt;`) that a user inputs into a comment box, and instead strips anything that looks like a tag from the comment entirely.

So, if you enter something like &amp;#96;&amp;lt;div&amp;gt;test&amp;lt;/div&amp;gt;&amp;#96; in the comment box, you would expect to see &amp;lt;div&amp;gt;test&amp;lt;/div&amp;gt; in the post but you would actually end up with `test`.

The exceptions that I've found are ``, ``, ``, ``, and `` tags.

The only reliable way to get around this odd implementation is to use the code tag with its content already HTML-encoded, just like you would if you were writing your own HTML. So entering something like &amp;lt;code&amp;gt;&amp;amp;lt;div&amp;amp;gt;test&amp;amp;lt;/div&amp;amp;gt;&amp;lt;/code&amp;gt; will give the expected result &amp;lt;div&amp;gt;test&amp;lt;/div&amp;gt;.

Note that you will also have to replace the back-ticks with `&amp;#96;`

FYI, here is the code I used to create this description itself. The same code is entered in the first comment below (note the difference where the back-ticks are used to surround this: `test`).</p> ]]></description>
<pubDate>Mon, 09 Nov 2009 11:57:52 GMT</pubDate>
<guid>http://snipplr.com/view/22799/snipplr-workaround-code-in-comments/</guid>
</item>
</channel>
</rss>