-
Notifications
You must be signed in to change notification settings - Fork 10.3k
PDF Viewer Has a Black/Grey Overlap on Rendered File (Firefox only) #8022
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
Comments
Unable to reproduce on Mac OS |
Same on Linux Debian Jessie and testing: not reproductible. |
@smajid25 can you paste graphics section from about:support ? |
What do you mean by graphics section from about:support? |
When using Firefox default pdf viewer it is also prevalent like the link I have provided above |
Sounds like regression from https://bugzilla.mozilla.org/show_bug.cgi?id=1303534 (which fixes #7556) |
Hmmmm so the first link says it will work right if HWA (Hardware Acceleration?) is disabled and from what I understand, from the second link, this is an upstream issue. So I am just curious as to what is the root cause of this issue and can this issue be resolved? |
I've filed the following two upstream bugs, since both of the issues are unfortunately regressions:
For tracking down regressions in Firefox, |
Just to confirm, this issue involves the Firefox browser and not the PDF.js, right? |
Correct, and only on windows with hwa enabled. |
Ok great, and is there a specific reason why this issue only applies to certain PDFs, because it only appears on 2 of the 5 PDFs that I tested. In other words what could I do to the PDFs I create/generate to avoid this issue from occurring in the first place? |
Based on upstream bug it's related to the specific sequence of clip() and restore() operations. |
I'm assuming that these two methods are involved in the rendering of the PDF's? I guess there's not much I can do on my end other than using less images in the PDF's I generate or avoid using images that trigger this. |
Is this still a problem on Windows? It works fine for me on Linux and given the age of the issue I'm wondering if this perhaps already got fixed upstream. @Snuffleupagus Could you perhaps check this on Windows? |
Unfortunately this is still just as broken as before, which isn't that surprising given that both of the bugs mentioned in #8022 (comment) are not yet fixed :-( |
Link to PDF file (or attach file here):
February Collision Generic PC R2-1.pdf
*****Note: Issue only appears on the first page of the documents ******
Configuration:
Steps to reproduce the problem:
What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
The text was updated successfully, but these errors were encountered: