You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click the first radio button on the second page. Notice that extra fields appear behind it.
Enter a date: 12-05-2024
Save the PDF file to disk.
Open the saved PDF file. Notice that the first radio button on the second page is checked, but the extra fields behind it are no longer visible. This makes it seem as if data loss occurred, even though that's not the case.
Click the second radio button below it and click the first radio button again. Notice that the extra fields behind the first radio button are now correctly visible, including the entered date.
timvandermeij
changed the title
Saving filled out
Extra fields not rendered after saving and opening a PDF file with AcroForms
May 12, 2024
timvandermeij
changed the title
Extra fields not rendered after saving and opening a PDF file with AcroForms
Fields not rendered anymore after saving and opening a PDF file with AcroForms
May 12, 2024
timvandermeij
changed the title
Fields not rendered anymore after saving and opening a PDF file with AcroForms
Fields not rendered after saving and opening Dutch tax form
May 12, 2024
I suppose the action under the A entry must be triggered even when there's no user action.
In the specs, we can read that:
The optional A entry in the annotation or outline item dictionary (see Tables 168 and 153) specifies an
action performed when the annotation or outline item is activated;...
I wonder when we should trigger the action: either when rendering the annotation for the first time or when all the annotations data are loaded in the sandbox (and before or after DcumentOpen/PageOpen...).
Today I found out that if I save the form with the PDF editor in Microsoft Edge and then open the PDF file with Firefox that it does render correctly, so that makes me think that the rendering part in PDF.js might work correctly but that it's rather a problem with saving the PDF file from PDF.js...
Attach (recommended) or Link to PDF file here:
Configuration:
Steps to reproduce the problem:
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://mozilla.github.io/pdf.js/web/viewer.html
The text was updated successfully, but these errors were encountered: