starred/documenso

Fork 0

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

[GH-ISSUE #2148] Checkbox Fields Shift During Signing Phase #626

New issue

Closed

opened 2026-02-26 18:47:49 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 18:47:49 +03:00

Owner

Originally created by @NDCallahan on GitHub (Nov 7, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2148

Issue Description

Checkbox elements placed during document composition do not retain their original coordinates during the signing phase. This misalignment occurs when overlaying checkboxes on an uploaded PDF, regardless of whether the PDF contains pre-existing checkbox graphics or fields.

Steps to Reproduce

Start a new document composition in Documenso.
Upload a PDF file as the base document (may or may not contain visual checkbox areas).
Drag and place one or more checkbox fields onto the document, aligning them with intended areas.
Save and proceed to the signing phase.
Observe the checkbox positions during signing.

Expected Behavior

Checkboxes should remain fixed at the coordinates where they were placed during composition, accurately reflecting the intended layout and alignment with the underlying PDF.

Current Behavior

During signing, checkbox elements shift from their original positions. They no longer align with the coordinates set during composition, resulting in visual misplacement and potential confusion for signers.

Screenshots (optional)

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

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 @NDCallahan on GitHub (Nov 7, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2148 ### Issue Description Checkbox elements placed during document composition do not retain their original coordinates during the signing phase. This misalignment occurs when overlaying checkboxes on an uploaded PDF, regardless of whether the PDF contains pre-existing checkbox graphics or fields. ### Steps to Reproduce 1. Start a new document composition in Documenso. 2. Upload a PDF file as the base document (may or may not contain visual checkbox areas). 3. Drag and place one or more checkbox fields onto the document, aligning them with intended areas. 4. Save and proceed to the signing phase. 5. Observe the checkbox positions during signing. ### Expected Behavior Checkboxes should remain fixed at the coordinates where they were placed during composition, accurately reflecting the intended layout and alignment with the underlying PDF. ### Current Behavior During signing, checkbox elements shift from their original positions. They no longer align with the coordinates set during composition, resulting in visual misplacement and potential confusion for signers. ### Screenshots (optional) <img width="186" height="158" alt="Image" src="https://github.com/user-attachments/assets/ce273b52-d5d5-43e0-a1e4-5864e979bcae" /> <img width="174" height="384" alt="Image" src="https://github.com/user-attachments/assets/cc443687-2039-4600-9dcf-30fc825b4f23" /> <img width="125" height="283" alt="Image" src="https://github.com/user-attachments/assets/d8dfe7b3-04e5-4670-be86-b5412fd4111e" /> <img width="198" height="364" alt="Image" src="https://github.com/user-attachments/assets/da148ff0-e336-43ab-826d-e3c3e0f00746" /> ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### 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

2026-02-26 18:47:49 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:50 +03:00

Author

Owner

@NDCallahan commented on GitHub (Nov 7, 2025):

If i strategically place it just like below, it is the closest I have gotten to it looking good when it's sent for signing

@NDCallahan commented on GitHub (Nov 7, 2025): If i strategically place it just like below, it is the closest I have gotten to it looking good when it's sent for signing <img width="144" height="137" alt="Image" src="https://github.com/user-attachments/assets/6a5fc9ce-44b7-4721-9935-338e579c1d4c" />

kerem commented

2026-02-26 18:47:50 +03:00

Author

Owner

@tanushree-coder-girl commented on GitHub (Nov 15, 2025):

Hi @NDCallahan I think this issue has been resolved. I tested it on the current version and I’m not able to reproduce it anymore.

@tanushree-coder-girl commented on GitHub (Nov 15, 2025): Hi @NDCallahan I think this issue has been resolved. I tested it on the current version and I’m not able to reproduce it anymore.

kerem commented

2026-02-26 18:47:50 +03:00

Author

Owner

@NDCallahan commented on GitHub (Nov 15, 2025):

you aare correct. v2 has solved this problem!

@NDCallahan commented on GitHub (Nov 15, 2025): you aare correct. v2 has solved this problem!

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#626

No description provided.

Rows
Columns