-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Bad font rendering on Linux #2927
Comments
can i use 'npm update' to fix this bug? |
So far the published version hasn't changed. You can work around this by using the BrowserFetcher to run a different Chromium revision: const browserFetcher = puppeteer.createBrowserFetcher();
const revisionInfo = await browserFetcher.download('576827');
const browser = await puppeteer.launch({ executablePath: revisionInfo.executablePath }) |
Thanks @slyrz for the workaround. We'll push an updated 1.6.1 shortly. |
For the record: upstream bug for this is https://crbug.com/857511 |
Puppeteer v1.6.1 is live with an updated chromium revision to address this bug. https://github.com/GoogleChrome/puppeteer/releases/tag/v1.6.1 |
@MrTurnRight I don't think this is related; there are quite a few reports with various solutions regarding Chinese fonts: https://github.com/GoogleChrome/puppeteer/issues?q=is%3Aissue+Chinese+is%3Aclosed |
thank you , i found the solution. im so sorry. |
@MrMitch how did you fix it? |
@Tusko I think you meant to mention @MrTurnRight and not me ;) |
@MrTurnRight , could you please share your solution? Thanks |
Tell us about your environment:
Just to let you know, 1.6.0 is pinned to a Chromium version with broken font rendering on Linux,
so screenshots for Linux users might look bad.
I think this was caused by a fontconfig update and was eventually fixed in this commit. This should give you the timespan of "broken" Chromium builds.
For comparison:
Revision 574897 (currently pinned)
Revision 576827 (latest build)
The text was updated successfully, but these errors were encountered: