starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-24 21:36:01 +03:00

[GH-ISSUE #2088] Signature process web page rendering issue #599

New issue

Open

opened 2026-02-26 18:47:44 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @nfranke on GitHub (Oct 22, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2088

Issue Description

When trying to sign a document via the document.com web page, the actual signature field is enormous and way, way down to the bottom left on the page.

Steps to Reproduce

Create PDF and use API to upload. Use API to send an email containing the signature link to the recipient. Click on the "View Document to sign" link and observe the issue.

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

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 @nfranke on GitHub (Oct 22, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2088 ### Issue Description When trying to sign a document via the document.com web page, the actual signature field is enormous and way, way down to the bottom left on the page. ### Steps to Reproduce Create PDF and use API to upload. Use API to send an email containing the signature link to the recipient. Click on the "View Document to sign" link and observe the issue. ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### 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

kerem added the

Stale

status: triage

labels

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

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Oct 22, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Oct 22, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

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

Author

Owner

@nfranke commented on GitHub (Oct 22, 2025):

I may have a clue. The bounds of the document are basically ignored when placing fields. If you place one that's outside of the document's bounds, it acts very odd.

@nfranke commented on GitHub (Oct 22, 2025): I may have a clue. The bounds of the document are basically ignored when placing fields. If you place one that's outside of the document's bounds, it acts very odd.

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Oct 22, 2025):

Hey @nfranke, I will investigate the document bounds issue, in the mean time, can I get the code you used for the API? That might help more in investigating the original issue.

@ephraimduncan commented on GitHub (Oct 22, 2025): Hey @nfranke, I will investigate the document bounds issue, in the mean time, can I get the code you used for the API? That might help more in investigating the original issue.

kerem commented

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

Author

Owner

@nfranke commented on GitHub (Oct 23, 2025):

I rewrote my code, so I don't have that. Basically, I put a signature field at like 200,400 initially thinking that was in points. After fixing that, it seems fine. I had a simple 2-page PDF generated via iText in Java.

@nfranke commented on GitHub (Oct 23, 2025): I rewrote my code, so I don't have that. Basically, I put a signature field at like 200,400 initially thinking that was in points. After fixing that, it seems fine. I had a simple 2-page PDF generated via iText in Java.

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Oct 24, 2025):

It should be in percentages, will open a pr to limit it between 0-100 to avoid this confusion in the future

@ephraimduncan commented on GitHub (Oct 24, 2025): It should be in percentages, will open a pr to limit it between 0-100 to avoid this confusion in the future

kerem referenced this issue

2026-02-26 19:31:42 +03:00

[PR #599] [MERGED] feat: email verification for registration #1070

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

No description provided.

Rows
Columns