-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🐛 Bug]: PDF generated on selenium nodes are missing some unicode characters [𝘽𝙍𝙐 U+1D63D] #2460
Comments
@quertenmont, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
I tried to search for something and saw this https://support.google.com/docs/thread/187910945/no-glyph-script-error?hl=en |
I saw you mentioned print the PDF. However, above ticket also mentioned
|
Also, can you provide what language is used in your PDF that has font issue? |
@VietND96 thanks for looking into it. Thanks in advance |
What happened?
Hello,
I am generating some pdf on a selenium node containg unicode characters like these: 𝘽𝙍𝙐 (i.e. U+1D63D )
Unfortunately, the generated pdf doesn't show those characters but have a "no glyph box" instead.
I have no issue when I print the pdf from my chrome brower, so I suppose that the issue is related to a missing font in the docker, but I don't know which one neither how to add it.
Could someone please help and batch the docker ?
Thanks in advance,
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
kubernetes
Docker Selenium version (image tag)
4.26
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: