Welcome to the Angular feedback portal. We’re happy you’re here! If you have feedback on how to improve the Angular, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Details:

When using the Angular Standalone PDF Viewer with a multi-page PDF, a signature field on a page that is not immediately rendered duplicates after updating other form fields programmatically.

Steps to reproduce:

  1. Open a PDF document with multiple pages (4 and more), with at least one signature field on the last page.
  2. Fill the signature field using the PDF Viewer UI and save/download the signed PDF.
  3. Open the signed PDF programmatically in the PDF Viewer.
  4. Update any other form field using
this method:
    pdfViewer.formDesigner.updateFormField()
  5. Scroll to the page containing the signature field (last page).
Expected Result:

The signature field displays exactly as saved, without duplication.

Actual Result:

The signature is rendered twice in the same signature field:

  • Once as originally saved
  • Once as a smaller duplicate

Notes:

  • The issue only occurs if the signature is on a page that is not rendered immediately (i.e., a page further down in the document)
  • Only updating other fields programmatically using `pdfViewer.formDesigner.updateFormField()` triggers the duplication when the signature page renders

Code Snippets:

Reproducible code sample on StackBlitz: code sample

The sample already uses a signed document and updates the text fields "First Name" and "Last Name" after `documentLoad` event.

To reproduce the bug, simply scroll to page 4 and observe the last signature field - one circle was placed originally, but two circles are displayed (original and small duplicated one in the center)

syncfusion-signature-bug.png