Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When making pdf output, bg image becomes invisible #293

Closed
nkjmsss opened this issue Oct 13, 2020 · 3 comments · Fixed by #294
Closed

When making pdf output, bg image becomes invisible #293

nkjmsss opened this issue Oct 13, 2020 · 3 comments · Fixed by #294
Labels
bug Something isn't working upstream Caused in upstream, not in this repo

Comments

@nkjmsss
Copy link

nkjmsss commented Oct 13, 2020

If image is loaded like below (as bg image), bg image becomes invisible. It only happens in pdf output.

![bg contain](img/sample.png)

I'm using Mac OS 10.15.6 and Node v12.16.2.

@yhatt
Copy link
Member

yhatt commented Oct 13, 2020

Didn't you see a warning message about local resources when generating PDF?

[  WARN ] Marp CLI has detected accessing to local file. That is blocked by security reason. Instead we recommend using assets uploaded to
          online. (Or you can use --allow-local-files option if you are understood of security risk)

Try using --allow-local-files option as written in warning.

@yhatt yhatt added the question 🙅 Not issue, just a question (should post to Marp discussion) label Oct 13, 2020
@yhatt
Copy link
Member

yhatt commented Oct 16, 2020

A reproducible example was provided in the issue tracker of Marp for VS Code (marp-team/marp-vscode#175), and I've confirmed not rendered background images in Marp CLI too.

Identify this issue as a bug, and going to find out a workaround to avoid a problem by upstream Chrome.

@yhatt yhatt added bug Something isn't working upstream Caused in upstream, not in this repo and removed question 🙅 Not issue, just a question (should post to Marp discussion) labels Oct 16, 2020
@yhatt
Copy link
Member

yhatt commented Oct 18, 2020

We will patch for workaround in the next release: #294. If you are still using the current release, you also can try using --template bare option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream Caused in upstream, not in this repo
Projects
None yet
2 participants