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

Display widget signature #13214

Merged
merged 1 commit into from
Apr 10, 2021
Merged

Conversation

calixteman
Copy link
Contributor

  • but don't validate them for now;
  • Firefox will display a bar to warn that the signature validation is not supported (see https://bugzilla.mozilla.org/show_bug.cgi?id=854315)
  • almost all (all ?) pdf readers display signatures;
  • validation is done in edge but for now it's behind a pref.

l10n/en-US/chrome.properties Outdated Show resolved Hide resolved
src/core/annotation.js Outdated Show resolved Hide resolved
src/core/document.js Outdated Show resolved Hide resolved
web/app.js Outdated Show resolved Hide resolved
@calixteman calixteman force-pushed the signatures branch 2 times, most recently from 31c3384 to 5bd4b8d Compare April 10, 2021 15:46
Copy link
Collaborator

@Snuffleupagus Snuffleupagus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any existing reference-tests which will cover these changes? If not, can you please add one?

(We probably want to defer this to a follow-up, but we should perhaps consider if/how we want to display a warning in the GENERIC-viewer as well.)

test/unit/api_spec.js Show resolved Hide resolved
Copy link
Collaborator

@Snuffleupagus Snuffleupagus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r=me, with passing tests; thank you!

@calixteman
Copy link
Contributor Author

/botio test

@pdfjsbot
Copy link

From: Bot.io (Windows)


Received

Command cmd_test from @calixteman received. Current queue size: 0

Live output at: http://3.101.106.178:8877/edf3a33c94c93e2/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_test from @calixteman received. Current queue size: 0

Live output at: http://54.67.70.0:8877/8c432dcf69fb386/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Failed

Full output at http://54.67.70.0:8877/8c432dcf69fb386/output.txt

Total script time: 25.07 mins

  • Font tests: Passed
  • Unit tests: Passed
  • Integration Tests: Passed
  • Regression tests: FAILED

Image differences available at: http://54.67.70.0:8877/8c432dcf69fb386/reftest-analyzer.html#web=eq.log

@pdfjsbot
Copy link

From: Bot.io (Windows)


Failed

Full output at http://3.101.106.178:8877/edf3a33c94c93e2/output.txt

Total script time: 28.55 mins

  • Font tests: Passed
  • Unit tests: Passed
  • Integration Tests: Passed
  • Regression tests: FAILED

Image differences available at: http://3.101.106.178:8877/edf3a33c94c93e2/reftest-analyzer.html#web=eq.log

@timvandermeij
Copy link
Contributor

@calixteman Unfortunately I don't have enough access rights to be able to comment on the upstream patch in Phabricator, but I found a bug in there: } else if ("signatures") { always evaluates to true. I think you meant } else if (featureId === "signatures") { there, but the featureId === part fell off.

  - but don't validate them for now;
  - Firefox will display a bar to warn that the signature validation is not supported (see https://bugzilla.mozilla.org/show_bug.cgi?id=854315)
  - almost all (all ?) pdf readers display signatures;
  - validation is done in edge but for now it's behind a pref.
@timvandermeij
Copy link
Contributor

/botio-linux preview

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_preview from @timvandermeij received. Current queue size: 0

Live output at: http://54.67.70.0:8877/f90cd937a5806b8/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Success

Full output at http://54.67.70.0:8877/f90cd937a5806b8/output.txt

Total script time: 4.39 mins

Published

@timvandermeij timvandermeij merged commit d9d626a into mozilla:master Apr 10, 2021
@timvandermeij
Copy link
Contributor

Looks good to me too; thanks! Let's do this, especially since we can now properly warn users about the missing validation and this has been requested very often.

/botio makeref

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_makeref from @timvandermeij received. Current queue size: 0

Live output at: http://54.67.70.0:8877/a96e7f77d1d93b3/output.txt

@pdfjsbot
Copy link

From: Bot.io (Windows)


Received

Command cmd_makeref from @timvandermeij received. Current queue size: 1

Live output at: http://3.101.106.178:8877/6767816e411abfa/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Success

Full output at http://54.67.70.0:8877/a96e7f77d1d93b3/output.txt

Total script time: 22.81 mins

  • Lint: Passed
  • Make references: Passed
  • Check references: Passed

@pdfjsbot
Copy link

From: Bot.io (Windows)


Success

Full output at http://3.101.106.178:8877/6767816e411abfa/output.txt

Total script time: 26.24 mins

  • Lint: Passed
  • Make references: Passed
  • Check references: Passed

@CetinSert
Copy link
Contributor

CetinSert commented Apr 11, 2021

@calixteman Can this be implemented for the SVG renderer as well?

@Snuffleupagus
Copy link
Collaborator

Can this be implemented for the SVG renderer as well?

Please note #13219 (comment)

moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Apr 12, 2021
…s not supported in PDF files r=bdahl DONTBUILD

Thanks to PR: mozilla/pdf.js#13214 signatures in PDF will be displayed but they won't be validated.
So display a banner to warn user about that.

Differential Revision: https://phabricator.services.mozilla.com/D111540
@stephanrauh
Copy link

@calixteman @timvandermeij Awesome! You've merged the PR roughly the same time when you've published the new version, so I'd like to ask if this is a feature of version 2.9? Or did you already include it in version 2.8?

@Snuffleupagus
Copy link
Collaborator

You've merged the PR roughly the same time when you've published the new version, so I'd like to ask if this is a feature of version 2.9? Or did you already include it in version 2.8?

This patch is not included in any official release yet, since it landed after the last release; see https://github.com/mozilla/pdf.js/releases and compare the date of this patch being merged with the date of the latest release :-)

Also, please keep in mind that all PDF.js versions consist of three numbers, e.g. the current pre-release is 2.8.335 and the stable release is 2.7.570. (In order to reduce confusion, it's always best to use full version numbers.)

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

Successfully merging this pull request may close these issues.

None yet

7 participants