</code></pre>
However, this workaround also applies to indented text or text in backticks:
-if you write <code>there is a bug involving the `<style>` tag</code>,
+if you write <code>there is a bug involving the \`<style>\` tag</code>,
or use indentation like
<pre><code>you can use this markup:
<style type="text/css">...</style>
</code></pre>
-then that gets turned into `<elyts` in the HTML too. This makes it quite
-difficult to talk about HTML on an IkiWiki instance (I had to use raw HTML in
+then that gets turned into `<elyts` in the source before passing through
+`markdown`, comes out as `<elyts` in the output HTML, and is rendered
+as `<elyts` by the browser. This makes it quite difficult to talk about
+HTML stylesheet markup on an IkiWiki instance (I had to use raw HTML in
this bug report's source to avoid the bug).
I think the side-effect of the workaround is more damaging than the actual bug
I thought it was some sort of misguided anti-cross-site-scripting filter...
--[[smcv]]
+
+> [[Fixed|done]] by passing the `MKD_NOSTYLE` flag to Discount instead.
+> Unfortunately this isn't bound by [[!cpan Text::Markdown::Discount]] yet,
+> so for now I'm hard-coding its numeric value. --[[smcv]]