iframes not being rendered correctly

[damienh]

We are using Pandoc in our jekyll site and it appears that iframes are being escaped illustrated below.

Here is our config file where we use pandoc to convert markdown to html

gems: [ 'jekyll-pandoc-multiple-formats' ]
pandoc:
  output: ./tmp
  flags: '--parse-raw --smart --section-divs'
  outputs:
    markdown: redcarpet

here is the iframe in our markdown file

<div class="scratch-preview">
    <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/26818098/?autostart=false" frameborder="0"></iframe>
    <img src="space-final.png">
</div>

If anyone can point me in the right direction it would be very much appreciated.

[nkalvi]

@damienh It looks like the four spaces indentation in front of the <iframe> makes it being treated as code blocks.

[mb21]

nkalvi is right, try the following markdown (note that the indentation is less than four spaces):

<div class="scratch-preview">
  <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/26818098/?autostart=false" frameborder="0"></iframe>
  ![](space-final.png)
</div>

[nkalvi]

@damienh Depending on your source, you could try -f markdown_strict too.

@jgm Could one turn off just markdown_in_html_blocks in a case like this?
Also, if the indentation is reduced in this case, the <iframe> element it wrapped in a <p><\p> in output. It may not be the desired output.

Extension: markdown_in_html_blocks

Standard markdown allows you to include HTML "blocks": blocks
of HTML between balanced tags that are separated from the surrounding text
with blank lines, and start and end at the left margin. Within
these blocks, everything is interpreted as HTML, not markdown;
so (for example), * does not signify emphasis.

Pandoc behaves this way when the markdown_strict format is used; but
by default, pandoc interprets material between HTML block tags as markdown.

[damienh]

Hey thanks for this. Just did a test and it renders correctly.

Much appreciated.

Damien

[damienh]

Also just tried -f markdown_strict as a flag and that works without needing to amend the indentation. Which is a bonus as we have around 300 of these iframes like that.

Cheers @nkalvi

[damienh]

Though just noticed that breaks these flags :( # Introduction { .intro } so they lose their styling id's

[jgm]

You can try:

-f markdown_strict+header_attributes

or turn off what you don't want:

-f markdown-markdown_in_html_blocks

+++ Damien Hogan [Jun 26 15 01:42 ]:

Though just noticed that breaks these flags :( # Introduction { .intro
} so they lose their styling id's

—
Reply to this email directly or [1]view it on GitHub.

References

1. iframes not being rendered correctly #2244 (comment)

[nkalvi]

@jgm -f markdown-markdown_in_html_blocks doesn't seem to produce the expected result (I cannot see any change).
-f markdown_strict+header_attributes works as expected with the snippets given here.