Thank you very much for your feedback and for sharing your experience.
The request is still marked as "Unplanned". This means that the issue is a valid feature requested, but it is not scheduled for implementation yet. Note, that we monitor the community interest in each logged feature in our Feedback Portal. Based on the interest shown from the community and our priority queue we consider its implementation in a future release.
I would suggest you subscribe to the issue in the Feedback Portal. Thus, you will be notified when the status of the issue is changed.
Posted on:21 Jul 2020 22:02
Wanted to check to see if there was any update on this or plans to support at least displaying acro form fields.
I had problems getting that example to work using the same version and CDN provided files that Telerik uses (https://cdnjs.cloudflare.com/ajax/libs/pdf.js/2.2.2/pdf.js), however, once I downloaded the PDF.js project from Github and built using GULP as the example explained, I could get the form fields to show as expected.
I'm almost betting that we could actually change the script-src from pointing at the CDN to the built files ourselves, however, because there are version differences AND telerik has wrappers around this library, I would suspect that issues would occur. So to me, it seems all Telerik needs to do is support the latest version of PDF.js and then expose some parameters to let you control the visibility of the form fields.
A few things to note though, in the current implementation of PDF.js in regards to form fields, (from my limited testing) it does not currently seem possible to update a field and have that feedback into the actual PDF. So if you try to download it, it'll download the original content stream without the modified form value. Additionally, on Adobe PDF's, it is possible to have a form field with MULTIPLE annotations/widgets, which are essentially locations for where to visually show the form field. In PDF.js, even though the fields are editable, it doesn't take into account scenarios where the form fields are actually linked.
These two issues will most likely cause confusion for users, so ideally either Telerik would need to implement this logic OR just render these fields as readonly.