-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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]: With dark theme, when pdfjs.forcePageColors is set to true, bright white flashes during page scroll (and other artifacts) #18680
Comments
Unfortunately just removing that is not a proper solution, since it'd result in other bugs by removing the "outline" for non-rendered pages. |
Thanks. Can you provide a link to an example of such a page so I can take a look? Hopefully someone with more knowledge of pdf.js can provide a working solution. |
Yes it can be a bit annoying for some users to have such flashing thing. |
You mean something like this? |
You're fast :) |
Attach (recommended) or Link to PDF file
https://cdn.fulltextarchive.com/wp-content/uploads/wp-advanced-pdf/1/The-Red-Badge-of-Couragex6045.pdf
https://www.adobe.com/support/products/enterprise/knowledgecenter/media/c4611_sample_explain.pdf
Web browser and its version
Firefox 129.0.2
Operating system and its version
Linux
PDF.js version
4.4.140
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
pdfjs.forcePageColors
totrue
inabout:config
.#fff
) page borders, even if the user has setpdfjs.pageColorsForeground
to a less bright colour.What is the expected behavior?
No white flashing when scrolling.
No bright white page borders in dark theme.
What went wrong?
Bright white flashing when scrolling.
Bright white page borders in dark theme, even when text foreground colour set to a less bright colour.
Link to a viewer
No response
Additional context
I found the problem and came to fix it. The problem arises from the
background-color
of the.pdfViewer .page
selector being set torgb(255 255 255)
inviewer.css
. When I remove that line of code, these issues are fixed.So I went to the master branch to remove that line from
viewer.css
and create a pull request to attach to this issue report. But I'm not seeing that line inviewer.css
.The text was updated successfully, but these errors were encountered: