[Bug Fix] :: Okular - Form Field propagation to other fields

Development Sponsored Work
1

Hi,

i can offer another 25 Euro for the fix of this Okular bug.

The problem here is that populated input fields are not immediately propagated (copied) to other input fields or in the document where the entered value is supposed to show up.

The bounty will be payed once the issue is fixed with both documents attached to the bug ticket.
Automatic Testcase to prevent regressions would be appreciated. If you have questions, feel free to
ask.

Cheers,
Andreas

2

Since we are now in 2024 - i can raise the bounty to 50 Euro for the fix.

3

Almost '25 - and i am willing to double the bounty to fix that issue. Bounty for the issue is now 100 Euro. I hope that is enough motivation for somebody to fix the issue.

4

I am trying this out a bit. Draft: Propagate form field changes to same name fields (!1220) · Merge requests · Graphics / Okular · GitLab

Let me know if your offer is still open and if you have other example PDFs I can try.

Consider the following: I do not consider adding the documents given in this comment because, right on opening, Okular says that it does not support the type of forms (XFA) that the example has.

5

Hi ulterno,

the offen is still perfectly valid. The form.pdf file that is attached to the poppler ticket Making sure you're not a bot! shows the problem as well. The file with the name ssa-820.pdf contains most likely a XFA form, so i guess you can ignore that for the moment.

The file from the okular ticket 450098 – PDF Form Fields are not propagated to other (non editable fields) - also shows the problem - so you have at least two files showing the problem.

Thanks for trying to fix the issue!

6

Hi,

the ticket actually now contains 3 files that show the problem. If all of them work after the fix - you will be awareded the proposed amount. I am following the progress of the ticket, but i cannot test.

Keep up the great work.

7

Thanks.

However, I realise I won’t be able to fulfil your request, so giving up on the bounty for now.

I will still finish the part that I am able to do though. i.e. propagation across simple forms with fields with the same name (as discussed by Christian González). So at least the other 2 should work.

Hopefully someone with more experience with PDFs will come and implement what you require.

8

Hi ulterno,

thanks for you effort anyway. I hope that somebody else will pickup your work and finishes it.

Cheers,

Andreas

9

I am trying to get the form field propagation by name, work for Radio buttons.
But when using a test document I made with LibreOffice Writer, the radio buttons in a groups end up having the same name in the PDF file. This seems to clash with the logic of ‘same-name ⇒ same value’, since only 1 radio button out of a group can be selected at a time.

It would be nice to have a document with working ‘Form Field propagation by name’ on Radio buttons, so that I could use it as a reference for completing that functionality, so please let me know if you get any.

Thanks

10

Hi, i have only the documents (three i think) that are linked to the ticket and not more. As far as i can remember the problem was always an input field (at least for me and the documents i provided).

11

Seems so, but the specification seems to say that it works on all types of Form Fields, so I was hoping that it would work with Radio buttons too and it would be good to have the feature be complete, if it’s going to be there.

Of course, this question was not about your bug, but just me, trying to find some way to get an example for what the specification implied. I’ll see if I can find an example somewhere else.

Thanks

12

Another year passed - raising the bounty to 150 Euro.