Rendering of inline images with relative paths is not working

The viewer panel does not render images that are in a path relative to the file being edited. It does render remote images just fine, however. Examples have been included that demonstrate a failed render and a successful render. In both cases, the Export/HTML command will produce a document that is able to render in a browser since the links are properly formatted in both example cases.

Example1 - render failure:

• Image exists in a relative directory: ./images
• File target for the markdown link: ./images/someImage.png
• Goal - render the image inline in the viewer panel
• Markdown - ![Test](./images/someImage.png)
• Result - Image is not rendered; an [X] placeholder is there instead

Example2 - render success:

• Image exists at a remote HTTP site: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png
• Goal - render the image inline in the viewer panel
• Markdown: ![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png)
• Result - Image is rendered without problems

[btbroot]

Neither GitHub’s Markdown renderer, nor Pandoc support “file:///” URI (security concerns?) Thus, requiring local files to be referred with “file” scheme makes Markdown files not really portable.

Please allow bare file paths (or “,/path”) in the image statements

[nea]

Hey @andrewanswer

Thanks a lot ^^ Yeah, when I worked on the fix for this I thought about that. But the parsing made it way easier with the file:/// prefix. But I’ll keep this on my desk to fine-tune the parser and renderer accordingly.

Cheers