Jupyter-book: iframe not rendering

Created on 30 Jan 2019  路  8Comments  路  Source: executablebooks/jupyter-book

I've created some interactive brain images using nilearn's plotting calls to brainsprite.js. The images look lovely in a jupyter notebook, and when I render the notebook with nbconvert they still look lovely and retain interactivity. But when I try to put the executed notebooks into jupyter-book, I get an unrendered iframe:

screenshot from 2019-01-30 15-28-37

Any ideas what could be going on here, or how to start tackling this ? Thanks as always !

Most helpful comment

in my case, I saw lots of "&" signs (I think it was &) and was like "huh that doesn't look like normal HTML". Then I looked up the encoding symbols in HTML and had my ah-hah moment :-)

All 8 comments

hmmmmmmmmm could you give a link to your repo? How does the iframe code look in the markdown?

Thanks for the quick reply ! The repo is here, but I realized the error is creeping in the nbconvert conversion to markdown (the conversion to html works fine). I'll close this since it doesn't seem to be a jupyter book problem :)

know what was going wrong? was it losing some text or something?

It looks like it's cutting in the middle -- attaching two text files here, one with what's rendered in the markdown doc and one with what's in the raw markdown text but not rendering in the markdown preview:

unrender_text.txt
rendered_text.txt

Edited to add: this is converting a different brainsprite, so the text might not match up exactly to what I previously reported, though the behavior is the same. I can also share text for the original sprite, if that's helpful !

ah - I think this is related to: https://github.com/jupyter/jupyter-book/issues/72

Thanks so much for the pointer ! That's super helpful.

A beginner question: there you were able to figure out that it was an unquoted col attribute. Any recommendations on how to track down the problem ? Or if you have other resources to point to, I'd appreciate it ! Sorry for the noise.

in my case, I saw lots of "&" signs (I think it was &) and was like "huh that doesn't look like normal HTML". Then I looked up the encoding symbols in HTML and had my ah-hah moment :-)

Update: unquoted attributes were exactly the problem :sparkles:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Cyb3rWard0g picture Cyb3rWard0g  路  5Comments

bsamadi picture bsamadi  路  3Comments

mmcky picture mmcky  路  5Comments

matrs picture matrs  路  3Comments

rickwierenga picture rickwierenga  路  3Comments