Image don't show in presentation mode

Bug graveyard
1

Steps to reproduce

  • Activate the plugin of Slides
  • Create a link to an image !()[image.jpg]
  • Preview the markdown. The image does show
  • Start presentation. The image doesn’t show

Expected result

A image in the slide

Actual result

A black dot or nothing

Environment

  • Operating system: MacOS Mojave
  • Obsidian version: 6.0
  • Using custom CSS: No

Additional information

5 Likes
2

Steps to reproduce

when using the presentation mode to view images.

Expected result

I expect the image to be displayed

Actual result

I get the link of image pathway ex- ![[image name. png]]

Environment

Windows 10 Surface pro
  • Operating system:
0.64
  • Obsidian version:
No
  • Using custom CSS:

Additional information

1 Like
3

@Silver should this be moved to plugin ideas?

4

I think it’s alright, slides is a core plugin that we provide after all. “Plugin ideas” is for new features that we think should be plugins instead.

1 Like
5

Same with following environment

Environment

  • Operating system: Linux - PopOs 20.04

  • Obsidian version - 0.6.7

  • Using custom CSS - No

1 Like
6

Hi! Same in version 0.7.3 on Windows 10. Was excited to find slides plugin but it’s not usable for me until this is fixed.

7

Same problem for me. It works with linked external images, but not with attachments :frowning:

8

Hadn’t noticed that, but yes, external images do work. I also can’t find a syntax that works for local images though. E.g. in the following, both images render correctly in the Markdown view of the note, but only the second shows up in the Presentation view:

---

![Image](testimg.jpg)

---

![Image](https://upload.wikimedia.org/wikipedia/en/9/95/Test_image.jpg)

---
9

Daer Kate. That’s correct. Your first line is the syntax for showing a local file (eg coming froma copy/paste) and that one doesn’t work. The second syntax is the one for an external file and that one works :slight_smile:

10

will be fixed in a future release.

1 Like
11

Has this been fixed yet? I have the same problem with V1.0.3

1 Like