Rendering problems on Chrome - overlapping characters and not readable letters in default view

[PawelW13i]

PDF file: 0939bfa0-731d-48ca-8c0b-ea110cdcf143.pdf

Configuration:

• Web browser and its version:
  Works fine on: Firefox - 97.0.2 (64 bity)
  Problem noticed on: Chrome 99.0.4844.51 (and lower)
• Operating system: Windows
• PDF.js version: latest (currently v2.13.216)

Steps to reproduce the problem:

1. Try to open attached PDF in Chrome (and in Firefox)
2. Check the "footer" - telephone, bankgiro and other words are not fully visible on Chrome

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

Problem was not spotted in version 2.7.570

One extra finding done recently - problem occurs on some subset of PDF's and they are coming from one "provider" - ABBY FineReader Engine 12

[tgreiser]

One of my clients has the same issue on Windows 11 Pro. Issue happens in Chrome as well as in electron (chromium). Seems specific to that computer. Reproduceable there, but not on other computers.

[breezyJake]

We use an older version of pdf.js to render pdf resume's and we are seeing the same issue on Chromium browsers intermittently. What information would be useful to narrow down this issue?

[RayHemm]

Some of our customers are using current DELL XPS 13 notebooks with Iris Graphics. They encounter the same issue with Chromium-based browsers. If you disable the hardware acceleration in Chrome the issue is gone. With Intel UHD we do not encounter any issues. No issues with AMD and NVIDIA.

[albertbal]

Same problem here. Verified it affects PDF.js versions from 2.8.335 to 2.14.305, and it doesn't affect version 2.7.570.

[Rstyl3]

I have the same issue and refreshing the page/canvas changes the missing fragments. The workaround I have, is to disable "Accelerated 2D canvas" in Chrome. You can check Here

[bmrinal]

is there any acknowledgement of issue from the maintainers? We are having the same issue. Any idea when this might be fixed?

[Snuffleupagus]

This document looks just fine in Firefox, which is the primary development target for the PDF.js library.
Hence it's not clear that it's necessarily an actionable bug here, and it may very well be a browser-bug (in Google Chrome).

[PawelW13i]

@Snuffleupagus it is a bit strange as it is actually working on PDF.js 2.7.570 and stops working on same browser version but on PDF.js 2.13.216. In our case there are multiple versions of PDF.js between but maybe others observed from what version to what they upgraded when they observed the issue.

[marco-c]

It is entirely possible that we started doing something that trips Chrome, especially given what @Rstyl3 mentioned regarding the problem disappearing when disabling hardware acceleration in Chrome.

[ToxicSmurf]

This document looks just fine in Firefox, which is the primary development target for the PDF.js library. Hence it's not clear that it's necessarily an actionable bug here, and it may very well be a browser-bug (in Google Chrome).

By primary dev target, do you mean only dev target? The Chrome extension hasn't been updated in three years.