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

Mark bespoke template as not-printable and apply fallback if Puppeteer is required in bespoke template #294

Merged
merged 3 commits into from
Oct 18, 2020

Conversation

yhatt
Copy link
Member

@yhatt yhatt commented Oct 17, 2020

Original report: marp-team/marp-vscode#175

Set printable flag to each templates, and fallback into bare template if tried Puppeteer conversion in not-printable template.

We've found sometimes background images using ![bg]() are not rendered in PDF if using bespoke template and Chrome >= 85. I've recognized this problem as a regression by Chromium, and we should take this workaround until Chrome was fixed.

We could have taken to always use bare template in Puppeteer required conversion, but we have a mid term plan for the new printable handout template (#261) so printable flag is smart solution to keep multiple printable templates.

(Probably) we can close #293.

Original report: marp-team/marp-vscode#175

If tried using not-printable template in Puppeteer-required conversion,
Marp CLI automatically fallbacks into bare template.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When making pdf output, bg image becomes invisible
1 participant