-
Notifications
You must be signed in to change notification settings - Fork 43
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
Editing PDF forms (and saving the results back to Nextcloud)? #354
Comments
I am surprised only 8 people gave 👍 Ideally, this issue should be resolved. But in the meantime: Is there a way to tell pdf.js that it should not make the form fields fillable? This wrongly suggests to the user that you can fill the form - bad UX - can someone make the designers/UX people of Nextcloud aware of this? |
Here is a screencast showing the problem on NC 27.1.3, pdfviewer 2.8.0 There is no way for the user to know that the entered data will not be saved. To the user, the lack of a save button does not mean it will not be saved, a lot of applications use auto-save. Ideally, the data entered into the form should be saved. If that is not possible/takes too much time to develop, maybe Nextcloud can tell pdf.js that it should not make the form fillable, so "read-only"? |
Just tested it on Firefox 125.0.3, on both NC 28.0.3 and NC 29.0.0 (cloud.nextcloud.com) the situation is still like in the screencast above (entered data not saved) #354 (comment) reopen @szaimen ? |
never mind, it works now in NC 29, thank you! |
It seems the upstream pdf.js supports editing and saving PDF forms (with saving added in v2.6.347). Any chance of supporting this in Nextcloud? I suppose adding the support to the viewer is just a matter of updating the pdf.js version, but maybe more work is needed to support saving? Not sure how this works, exactly...
The text was updated successfully, but these errors were encountered: