Obsidian version: v1.1.9
Installer version: v1.1.9
Operating system: Windows 10 Pro 10.0.19045
Login status: logged in
Catalyst license: vip
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on
I’m not exactly sure what you mean. Everything functions correctly, as in there is an image and there is also a functional link. So it’s clearly supported. It’s only the visual output which is a bit messed up.
I think we’re talking about different things. Your question which I quoted was about a local vault path being recognised. My reply was to say that the local vault path is indeed being parsed and turned into an image.
In the help docs there is an image with a local path (“og-image.png”):
And the CommonMark spec says that this is valid Markdown to encapsulate an image with a link in this way, so going back to my first post it looks like there is a bug with the conversion to HTML elements in the reading view.
For a remote image, the entire item wrapped in the link is clickable as a link which is what you’d expect:
For a local image, the item which is wrapped in the link is not a clickable as a link:
You can click the little link icon which is handy as it means they’re still partially usable.
I don’t believe that the expected behaviour for a wrapped local item should be that only the little icon is clickable. I assume it should be the same as a remote image in that the whole wrapped item is clickable.