Skip to content
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

PDF Viewer Has a Black/Grey Overlap on Rendered File (Firefox only) #8022

Closed
smajid25 opened this issue Feb 3, 2017 · 16 comments
Closed

PDF Viewer Has a Black/Grey Overlap on Rendered File (Firefox only) #8022

smajid25 opened this issue Feb 3, 2017 · 16 comments

Comments

@smajid25
Copy link

smajid25 commented Feb 3, 2017

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:

  • Web browser and its version: FireFox latest version
  • Operating system and its version: Windows 10 OS
  • PDF.js version: Current Stable version
  • Is an extension: No

Steps to reproduce the problem:

  1. Use pdf.js and place link inside source
  2. Open with all browsers
  3. Problem will be seen in Firefox only and appear normal in IE and Firefox

What is the expected behavior? (add screenshot)
normalbackground

What went wrong? (add screenshot)
blackbackground

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

@smajid25 smajid25 changed the title PDF.JS Has a Black/Grey Background PDF Viewer Has a Black/Grey Overlap on Rendered File Feb 3, 2017
@smajid25 smajid25 changed the title PDF Viewer Has a Black/Grey Overlap on Rendered File PDF Viewer Has a Black/Grey Overlap on Rendered File (Firefox) Feb 3, 2017
@smajid25 smajid25 changed the title PDF Viewer Has a Black/Grey Overlap on Rendered File (Firefox) PDF Viewer Has a Black/Grey Overlap on Rendered File (Firefox only) Feb 3, 2017
@yurydelendik
Copy link
Contributor

Unable to reproduce on Mac OS

@SamyCookie
Copy link

Same on Linux Debian Jessie and testing: not reproductible.

@yurydelendik
Copy link
Contributor

@smajid25 can you paste graphics section from about:support ?

@smajid25
Copy link
Author

smajid25 commented Feb 3, 2017

What do you mean by graphics section from about:support?
I haven't tested this on Mac OS yet, but when using this link below the problem should be prevalent. Open with Firefox on Windows 10 OS:

https://s3.amazonaws.com/VCUSA/WPP/assets+/MarketingAssets/January%20Collision%20Generic%20PC%20R1-3.pdf

@smajid25 smajid25 closed this as completed Feb 3, 2017
@smajid25 smajid25 reopened this Feb 3, 2017
@smajid25
Copy link
Author

smajid25 commented Feb 3, 2017

When using Firefox default pdf viewer it is also prevalent like the link I have provided above

@yurydelendik
Copy link
Contributor

Sounds like regression from https://bugzilla.mozilla.org/show_bug.cgi?id=1303534 (which fixes #7556)

@smajid25
Copy link
Author

smajid25 commented Feb 3, 2017

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?
Also thank you looking into this issue, I appreciate the quick responses.

@Snuffleupagus
Copy link
Collaborator

Snuffleupagus commented Feb 3, 2017

I've filed the following two upstream bugs, since both of the issues are unfortunately regressions:


For tracking down regressions in Firefox, mozregression can be used; please see http://mozilla.github.io/mozregression/ for more information.

@smajid25
Copy link
Author

smajid25 commented Feb 6, 2017

Just to confirm, this issue involves the Firefox browser and not the PDF.js, right?

@yurydelendik
Copy link
Contributor

Just to confirm, this issue involves the Firefox browser and not the PDF.js, right?

Correct, and only on windows with hwa enabled.

@smajid25
Copy link
Author

smajid25 commented Feb 6, 2017

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?

@yurydelendik
Copy link
Contributor

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.

@smajid25
Copy link
Author

smajid25 commented Feb 6, 2017

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.

@timvandermeij
Copy link
Contributor

timvandermeij commented Apr 25, 2021

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?

@Snuffleupagus
Copy link
Collaborator

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 :-(

@Snuffleupagus
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants