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

Apply workaround for vanished <marp-auto-scaling> component in Chrome 105+ #312

Merged
merged 3 commits into from
Aug 11, 2022

Conversation

yhatt
Copy link
Member

@yhatt yhatt commented Aug 11, 2022

I found sometimes the content of <marp-auto-scaling> component may not render in the first rendering of Chrome/Chromium 105 beta and later. Computing DOM positions is correct but contents are not painted at the first time.

Because of this problem, yhatt/marp-cli-example is temporally using Chromium 104 provided by the old Puppeteer, instead of the latest Chromium 105.
yhatt/marp-cli-example@b246940

I don't know the clear reason why, but I guess nested shadow DOMs may prevent painting the content of SVG. Flushing <svg> element by changing display style will render. Thus, I've patched to <marp-auto-scaling> component to flush display style on mounted.

By adopting the updated component, I've confirmed to fix vanished auto-scaling content when exporting image by Marp CLI.

@yhatt yhatt merged commit d8db5fa into main Aug 11, 2022
@yhatt yhatt deleted the workaround-for-vanished-auto-scaling-component branch August 11, 2022 15:45
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.

None yet

1 participant