X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/af94275af1c168bd51a620d9998ead93892cfd5d..63e6fa68b09efd88a28f4f684758500c74afcd10:/doc/bugs/escaped_style_tag_becomes_elyts.mdwn

diff --git a/doc/bugs/escaped_style_tag_becomes_elyts.mdwn b/doc/bugs/escaped_style_tag_becomes_elyts.mdwn
index 24d8fbf7e..336e2ff95 100644
--- a/doc/bugs/escaped_style_tag_becomes_elyts.mdwn
+++ b/doc/bugs/escaped_style_tag_becomes_elyts.mdwn
@@ -7,7 +7,7 @@ $r=~s/<elyts/<style/ig;
 </code></pre>
 
 However, this workaround also applies to indented text or text in backticks:
-if you write <code>there is a bug involving the `&lt;style&gt;` tag</code>,
+if you write <code>there is a bug involving the \`&lt;style&gt;\` tag</code>,
 or use indentation like
 
 <pre><code>you can use this markup:
@@ -15,8 +15,10 @@ or use indentation like
     &lt;style type="text/css"&gt;...&lt;/style&gt;
 </code></pre>
 
-then that gets turned into `&lt;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 `&lt;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
@@ -26,3 +28,7 @@ discuss style markup several times. The first couple of times I saw this happen,
 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]]