-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Failed to export local image when using gaia theme #175
Comments
We've confirmed reproducibility. Start finding out the root cause. Probably marp-team/marp-cli#293 is pointing out a similar problem.
|
I'm guessing this bug comes from Chrome/Chromium. Marp internally converts HTML into PDF through installed Chrome. I've confirmed there is often a broken advanced background image for inline SVG mode if printed the exported HTML to PDF through Chrome >= 85 on macOS. It happens in any theme, not limited to gaia theme.
I'll continue working for finding out the workaround. |
Thank you for your great work! I was able to make my work finished by exporting my slide as a HTML file and print it out as a PDF file. I'm very glad if my example files help to find the root cause of this issue. |
Reporting details to Chromium bug tracker helps to resolve the root cause. I found out the exported HTML in Marp CLI with bare template can render background images correctly. We were supposed to have designed the default template ( We will implement to Marp CLI the fallback of using bare templatewhen running Chromium-based conversion. |
Original report: marp-team/marp-vscode#175 If tried using not-printable template in Puppeteer-required conversion, Marp CLI automatically fallbacks into bare template.
When I export the following markdown with marp-vscode,
the result is this.
However, when I used default theme (drop the
theme: gaia
line), marp for VSCode exports local image correctly.Sample markdown and image are here. https://github.com/AseiSugiyama/marp_test
I guess this issue is not caused by #134 , so I opened this new issue.
The text was updated successfully, but these errors were encountered: