We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://cdnfile.yaomaitong.net/ksh/pdfcee021527e874f3587b2f25e53dbb390.pdf
Android browser ,I use millet Chrome 129.0.6668.100
Android 15
4.7.76
Yes
No
Duplicate address:https://github.com/trry-hub/issues/tree/pdfjs
Normal display
Normal display in chrome
Font overlap
No response
The text was updated successfully, but these errors were encountered:
Android browser
That's surprising, because the built-in Android browser uses Chrome.
Sorry, something went wrong.
Android browser That's surprising, because the built-in Android browser uses Chrome. If you open the same PDF at https://mozilla.github.io/pdf.js/web/viewer.html in that browser, do you see the same bug? Can you check what is the equivalent Chrome version to the browser you are using?
The preview at https://mozilla.github.io/pdf.js/web/viewer.html does not have any issues, and I have completed the Chrome version.
I confirm the bug in Chrome on a pixel 7 in opening this pdf in https://mozilla.github.io/pdf.js/web/viewer.html but that's fine with Firefox.
No branches or pull requests
Attach (recommended) or Link to PDF file
https://cdnfile.yaomaitong.net/ksh/pdfcee021527e874f3587b2f25e53dbb390.pdf
Web browser and its version
Android browser ,I use millet Chrome 129.0.6668.100
Operating system and its version
Android 15
PDF.js version
4.7.76
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
Duplicate address:https://github.com/trry-hub/issues/tree/pdfjs
What is the expected behavior?
Normal display
Normal display in chrome
What went wrong?
Font overlap
Link to a viewer
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: