Closed jrmiller82 closed 4 years ago
Ahhh. It's a hugo v60 and onwards effect of their new markdown parser. See discussion here: https://discourse.gohugo.io/t/raw-html-getting-omitted-in-0-60-0/22032/5
Can be fixed by adding the following to your hugo config.toml:
[markup.goldmark.renderer]
unsafe= true
Maybe this is something get added to the documentation on table styling?
Maybe this is something get added to the documentation on table styling?
No, it's not just table styling. I recommend putting that setting in your site's config.toml if using ox-hugo.
I am already tracking this at this pinned issue https://github.com/kaushalmodi/ox-hugo/issues/307:
It was quite silly for the Hugo developer to change the default behavior of allowing inline HTML when upgrading from BlackFriday to Goldmark. Little bit more of my venting on that topic: here and here.
So when #307 is implemented, the docs will state that the unsafe=true configuration is needed for goldmark? I don't really care where in the docs it is stated, just that is is stated somewhere. My thought is that users shouldn't need to reference github issues to implement items / examples that are already in the docs.
So when #307 is implemented, the docs will state that the unsafe=true configuration is needed for goldmark?
That's correct. I referenced that issue and closed this one as this is very closely related to an already open issue.
org text looks like this:
And
C-c C-e H H
leads to the following markdown:Which then gives us the following html:
See the
<!--raw HTML omitted -->
? That's the unexpected behavior.