[XFA] Selections of checkboxes or radio buttons are not saved (on a specific document)
Categories
(Firefox :: PDF Viewer, defect)
Tracking
()
People
(Reporter: danibodea, Unassigned)
References
Details
Attachments
(2 files)
+++ This bug was initially created as a clone of Bug #1723734 +++
Note
- When the user loads a specific PDF file in Adobe Reader, selects some radio buttons, and then saves it and reopens it, he will notice that the radio button selections previously made are not being shown.
Affected versions
- Beta v93.0b8
Affected platforms
- all
Steps to reproduce
- Launch browser.
- Load the attached PDF file.
- Make some radio button selections.
- Save the PDF file.
- Reopen it in either Firefox or Adobe Reader.
Expected result
- The radio button selections are properly displayed.
Actual result
- The radio button selections are not shown.
Regression range
- Not a regression.
Additional information
- This issue does not occur on all the radio buttons, but specifically on that set.
- The rendering of the selected radio button appears to be different than other radio button selections in other documents.
- Based on the above arguments, I've set the severity to S3.
| Reporter | ||
Comment 1•5 years ago
|
||
Radio button selections are rendered differently than in other documents.
| Reporter | ||
Comment 2•5 years ago
|
||
It might be important to note that if the user saves some radio button selections in Adobe Reader, those will be properly shown in Adobe, but not in Firefox.
Comment 3•5 years ago
|
||
The radio sizes are set in pdf and their width is 8px which is a bit small.
It seems that there are some inconsistencies between the rendering of radio buttons at different sizes:
<input type="radio" style="width:6px; height:6px" checked/>
<input type="radio" style="width:8px; height:8px" checked/>
<input type="radio" style="width:10px; height:10px" checked/>
<input type="radio" style="width:12px; height:12px" checked/>
shows different rendering (it's more consistent in chrome).
Comment 4•5 years ago
|
||
I confirm that something is wrong when saving the form.
The exclGroup for the first buttons is named (YesNoGroup) and the path in datasets seems to be correct.
So it's likely a binding issue.
| Reporter | ||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
In fact the two checkboxes for the question 1 have a <bind match="none"> which explicitly means that their values don't match with something in the datasets. So it's typically a form which needs to be printed and cannot be saved.
Updated•5 years ago
|
Updated•5 years ago
|
Description
•