-
Notifications
You must be signed in to change notification settings - Fork 10
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: Signature not displaying in Firefox #7683
Comments
Just a note for this: IF this signature is applied electronically and is considered a layer in the document like the eSigned sig, it may be the same issue we moved away from in the other viewer implementation. That old implementation relied on pdf.js (by Mozilla), which is also used natively in Firefox. |
Good news on this front: the |
@kkoskelin Here is the offending PDF. |
The above link has a PDF which has been altered (sanitized?) in some manner. However, this one appears to have the signature we desire for purposes of testing: esig.pdf |
Signature display is available in Firefox beta (89) so next release will have it. |
Many thanks, @calixteman for the update! Since a fix is forthcoming for Firefox and the number of affected internal users (those for whom it is most critical to see signatures) are using chrome/edge, closing this. |
Describe the Bug
The signature of an IRS attorney is not showing up in Firefox. It displays on the PDF in Chrome.
View of document in Chrome:
View of same document in Firefox:
Business Impact/Reason for Severity
In which environment did you see this bug?
Who were you logged in as?
What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
To Reproduce
Steps to reproduce the behavior:
Expected Behavior
*PDFs (including signatures on them) should display consistently across browsers
Actual Behavior
A clear and concise description of what actually happened.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Cause of Bug, If Known
Process for Logging a Bug:
Severity Definition:
Critical Defect
Blocks entire system's or module’s functionality
No workarounds available
Testing cannot proceed further without bug being fixed.
High-severity Defect
Affects key functionality of an application
There's a workaround, but not obvious or easy
App behaves in a way that is strongly different from the one stated in the requirements
Medium-severity Defect
A minor function does not behave in a way stated in the requirements.
Workaround is available and easy
Low-severity Defect
Mostly related to an application’s UI
Doesn't need a workaround, because it doesn't impact functionality
Definition of Done (Updated 4-14-21)
Product Owner
Engineering
The text was updated successfully, but these errors were encountered: