There is still a problem with local image links.

[jmcd040]

I'm reopening this after testing a bit more (WM3 Beta 8, Windows 10, Chrome). I assume you fully expect some of these results but the fact that some things partially work and others that should don't, has confused me so I wanted to figure out what was happening. I hope this chart and my conclusions below are at least a little helpful and may clarify some things for others who stumble on this.

Link Form	Image shows in Edit pane	Image shows in Preview Pane	Image Shows in Chrome Browser
	Yes	Yes	Yes
	No	Yes	Yes
	Yes	Yes	No
![Name]("C:\PathNoSpaces\img.jpg")	Yes	No	No
	No	No	No
![Name]("C:/Path with spaces/img.jpg")	Yes	No	No
![Name]("C:\Path with spaces\img.jpg")	Yes	No	No

The results are (I can only test this in Windows 10):

1. No file spec containing spaces (which is a legal file spec in windows) will produce images in all three of the editor, preview and browser.
2. Adding a title to an otherwise valid image link will keep it from being displayed in the editor (alone).

The only image link that displays images in the edit pane, preview and browser is one that uses forward slashes, does not bracket the pathname in quotations and contains no spaces in the pathname.

[writemonkey]

Thanks for that! The problem is I have little or no control over how image links are interpreted at export. I can only fully control inline images. i.