starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1260] Checkbox/radio buttons issues when using some characters in text #349

New issue

Open

opened 2026-02-26 18:46:38 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:46:38 +03:00

Owner

Originally created by @matevz-spacapan on GitHub (Jul 28, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1260

Originally assigned to: @GARY121github on GitHub.

Issue Description

EDIT: It seems that special characters are NOT the cause of the issue, but , is. Nonetheless, leaving the original text below, just in case.
If special characters (in my case these are č, š or ž) are used in radio buttons or checkboxes, then these fields will not work correctly when signing the document or when viewing a signed document. The specific issues are in the current behaviour section.

Steps to Reproduce

Create a template
Create a checkbox/radio button field and fill it with data with special characters (in my case these are č, š or ž)
Save the template
Send the template for signing
Select fields (issues may happen now already - see current behaviour)
Sign the document
Open the document (some issues are present here - see current behaviour)

Expected Behavior

No response

Current Behavior

radio buttons don't actually appear selected in the signed document (i.e. looks like no choice is made)
checkboxes don't seem to work correctly with the provided limits (I set an exactly 1 limit and the "Next field" button is still pointing to the checkbox after one is selected - the error TRPCClientError: {"code":"UnknownError","message":"You need to select exactly 1 options"} is sent in the console
similarly as above, selecting checkboxes shows an Error popup; it's almost impossible to un-select them or re-select them. The same error as above is printed in the console.

Screenshots (optional)

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

127.0.6533.72

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @matevz-spacapan on GitHub (Jul 28, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1260 Originally assigned to: @GARY121github on GitHub. ### Issue Description EDIT: It seems that special characters are NOT the cause of the issue, but `,` is. Nonetheless, leaving the original text below, just in case. If special characters (in my case these are `č`, `š` or `ž`) are used in radio buttons or checkboxes, then these fields will not work correctly when signing the document or when viewing a signed document. The specific issues are in the current behaviour section. ### Steps to Reproduce 1. Create a template 2. Create a checkbox/radio button field and fill it with data with special characters (in my case these are `č`, `š` or `ž`) 3. Save the template 4. Send the template for signing 5. Select fields (issues may happen now already - see _current behaviour_) 6. Sign the document 7. Open the document (some issues are present here - see _current behaviour_) ### Expected Behavior _No response_ ### Current Behavior - radio buttons don't actually appear selected in the signed document (i.e. looks like no choice is made) - checkboxes don't seem to work correctly with the provided limits (I set an exactly 1 limit and the "Next field" button is still pointing to the checkbox after one is selected - the error `TRPCClientError: {"code":"UnknownError","message":"You need to select exactly 1 options"}` is sent in the console - similarly as above, selecting checkboxes shows an Error popup; it's almost impossible to un-select them or re-select them. The same error as above is printed in the console. ### Screenshots (optional) ![Screenshot 2024-07-28 173430](https://github.com/user-attachments/assets/62719d46-97cd-4f40-95f3-dad95966fd23) ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] 127.0.6533.72 ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [X] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [X] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem added the

Stale

status: triage

labels

2026-02-26 18:46:38 +03:00

kerem commented

2026-02-26 18:46:38 +03:00

Author

Owner

@jvalvarenga commented on GitHub (Jul 29, 2024):

I would love to pick this up.

@jvalvarenga commented on GitHub (Jul 29, 2024): I would love to pick this up.

kerem commented

2026-02-26 18:46:38 +03:00

Author

Owner

@catalinpit commented on GitHub (Aug 8, 2024):

Hey @matevz-spacapan, thanks for reporting this!

@jvalvarenga, feel free to start the work on this. I've assigned it to you. Thanks!

@catalinpit commented on GitHub (Aug 8, 2024): Hey @matevz-spacapan, thanks for reporting this! @jvalvarenga, feel free to start the work on this. I've assigned it to you. Thanks!

kerem commented

2026-02-26 18:46:38 +03:00

Author

Owner

@jvalvarenga commented on GitHub (Aug 10, 2024):

Hey @matevz-spacapan, thanks for reporting this!

@jvalvarenga, feel free to start the work on this. I've assigned it to you. Thanks!

Thank you

@jvalvarenga commented on GitHub (Aug 10, 2024): > Hey @matevz-spacapan, thanks for reporting this! > > @jvalvarenga, feel free to start the work on this. I've assigned it to you. Thanks! Thank you

kerem commented

2026-02-26 18:46:38 +03:00

Author

Owner

@GARY121github commented on GitHub (Sep 11, 2024):

@catalinpit can I work on this issue, if it is still unsolved?

@GARY121github commented on GitHub (Sep 11, 2024): @catalinpit can I work on this issue, if it is still unsolved?

kerem commented

2026-02-26 18:46:38 +03:00

Author

Owner

@catalinpit commented on GitHub (Sep 11, 2024):

@catalinpit can I work on this issue, if it is still unsolved?

I've assigned the issue to you. Thanks!

@catalinpit commented on GitHub (Sep 11, 2024): > @catalinpit can I work on this issue, if it is still unsolved? I've assigned the issue to you. Thanks!

kerem referenced this issue

2026-02-26 19:30:57 +03:00

[PR #349] [MERGED] feat: update marketing mobile nav #900

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#349

No description provided.

Rows
Columns