Created attachment 76107 [details] ODT file with 2 radio buttons in the same group See attached files, ODT file has 2 radio buttons in the same group, allowing only one to be selected at a time. In PDF file, the buttons can both be selected at the same time as if not in the same group. Reason for this appears to be that the wrong property is used in the PDF document to indicate the group name.
Created attachment 76108 [details] ODT file export in PDF
Bug detected on 3.6.4.3, tested also on 4.0.1.2
Also present in 3.5.4.2 (Debian).
Bug detected on Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) on Windows 7 Professional 64bit tested with following pdf reader: - Mozilla Firefox 20.0.1 - Built-in PDF viewer - no function - evince 2.32.0.145 - no function - Adobe Acrobat Reader 11.0.2 - radio buttons could be selected, but not deselected - groups are not recognized - Foxit Reader 6.0.2.0413 - radio buttons could be selected, but not deselected - groups are not recognized rechecked with LibreOffice Version 4.0.3.3 (Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539) changes: - evince 2.32.0.145 - radio buttons could be selected, but not deselected - groups are not recognized
In libreoffice 4.0.4 (writer) I have the same problem, however I found a way to make it work. The group property must be empty, the name of the radios must be the same, preferably the standard name for radio buttons (in Italian: Pulsante di scelta #) as a different name seemed not to work. Honestly I didn't spend much time debugging or trying to determine if this is intended but I thought it was worth adding this report here.
I was in the same problem, but after read the "help web page" of LibreOffice: https://help.libreoffice.org/Common/Form_Controls#Option_Button. I have realized that seems like is not a bug.
*** Bug 90769 has been marked as a duplicate of this bug. ***
Seems to be fixed in LibreOffice 4.4.2.2
Created attachment 114990 [details] zip with pdf's from test documents from issue 61691 and 90769 thanks Jurgen for finding this and updating.. However, I see that your document behaves properly in 4.4.3.1 and 5.0.0.alpha1, but the sample document from this issue does not..