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

SVG-filters, for transfer maps, are not applied in the Firefox PDF Viewer #16143

Closed
Snuffleupagus opened this issue Mar 9, 2023 · 1 comment · Fixed by #16153
Closed

SVG-filters, for transfer maps, are not applied in the Firefox PDF Viewer #16143

Snuffleupagus opened this issue Mar 9, 2023 · 1 comment · Fixed by #16153

Comments

@Snuffleupagus
Copy link
Collaborator

Attach (recommended) or Link to PDF file here: https://github.com/mozilla/pdf.js/blob/master/test/pdfs/issue6931_reduced.pdf

Configuration:

  • Web browser and its version: Firefox Nightly 112
  • Operating system and its version: Windows 11
  • PDF.js version: 3.5.34 [a0ef5a4]
  • Is a browser extension: N/A

Steps to reproduce the problem:

  1. Load https://mozilla.github.io/pdf.js/web/viewer.html
  2. Open issue6931_reduced.pdf in the demo viewer.
  3. Open issue6931_reduced.pdf directly in Firefox.

What is the expected behavior? (add screenshot)
Since the demo viewer and the built-in Firefox PDF Viewer uses the same PDF.js version, rendering should be identical; note the correct rendering in the demo viewer:

demo

What went wrong? (add screenshot)
It appears that the SVG-filter, for the transfer map, isn't actually applied in the built-in Firefox PDF Veiwer:

builtin

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

/cc @calixteman

@calixteman
Copy link
Contributor

Oh! I discovered the same bug and filed a bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1821408

(I missed the gh mail)

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

Successfully merging a pull request may close this issue.

2 participants