[GH-ISSUE #877] Fix overflow of text on signing pad #267

Closed
opened 2026-02-26 18:46:12 +03:00 by kerem · 7 comments
Owner

Originally created by @plxity on GitHub (Jan 27, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/877

Originally assigned to: @Nisarg-Sha on GitHub.

Issue Description

Currently, the name is overflowing out of the signature section on landing page.

Steps to Reproduce

  1. Visit https://documenso.com/
  2. Type the name on the demo PDF given

Expected Behavior

Text-wrap should be there

Current Behavior

Text is overflowing

Screenshots (optional)

Screenshot 2024-01-27 at 12 39 23 PM

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 @plxity on GitHub (Jan 27, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/877 Originally assigned to: @Nisarg-Sha on GitHub. ### Issue Description Currently, the name is overflowing out of the signature section on landing page. ### Steps to Reproduce 1. Visit https://documenso.com/ 2. Type the name on the demo PDF given ### Expected Behavior Text-wrap should be there ### Current Behavior Text is overflowing ### Screenshots (optional) <img width="1024" alt="Screenshot 2024-01-27 at 12 39 23 PM" src="https://github.com/documenso/documenso/assets/28510494/736bec79-a8f8-4a58-99d7-e1e4493c7335"> ### 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. - [X] I want to work on creating a PR for this issue if approved
Author
Owner

@maige-app[bot] commented on GitHub (Jan 27, 2024):

Thank you for reporting the issue. It has been labeled as a bug and requires user interface changes. The issue will also be flagged for testing once the fix is implemented. If you're planning to work on a PR for this, please ensure to include tests for the new behavior.

From Maige. How's my driving?

<!-- gh-comment-id:1913047729 --> @maige-app[bot] commented on GitHub (Jan 27, 2024): Thank you for reporting the issue. It has been labeled as a bug and requires user interface changes. The issue will also be flagged for testing once the fix is implemented. If you're planning to work on a PR for this, please ensure to include tests for the new behavior. <sub>From [Maige](https://maige.app). How's my driving?</sub>
Author
Owner

@Nisarg-Sha commented on GitHub (Jan 27, 2024):

Can I Work on this issue ?

<!-- gh-comment-id:1913123100 --> @Nisarg-Sha commented on GitHub (Jan 27, 2024): Can I Work on this issue ?
Author
Owner

@dguyen commented on GitHub (Jan 29, 2024):

I think visually signatures should not wrap, but be scaled down

[X] I want to work on creating a PR for this issue if approved

I noticed you checked this @plxity, and also noticed you thumbs upped @Nisarg-Sha's comment

Are agreeing to let @Nisarg-Sha to work on this issue?

<!-- gh-comment-id:1914079713 --> @dguyen commented on GitHub (Jan 29, 2024): I think visually signatures should not wrap, but be scaled down > [X] I want to work on creating a PR for this issue if approved I noticed you checked this @plxity, and also noticed you thumbs upped @Nisarg-Sha's comment Are agreeing to let @Nisarg-Sha to work on this issue?
Author
Owner

@plxity commented on GitHub (Jan 29, 2024):

@dguyen Yes, @Nisarg-Sha can pick it up.

<!-- gh-comment-id:1914877805 --> @plxity commented on GitHub (Jan 29, 2024): @dguyen Yes, @Nisarg-Sha can pick it up.
Author
Owner

@plxity commented on GitHub (Feb 8, 2024):

@Nisarg-Sha If you are not working on it, I can pick it up. Let me know.

<!-- gh-comment-id:1933459622 --> @plxity commented on GitHub (Feb 8, 2024): @Nisarg-Sha If you are not working on it, I can pick it up. Let me know.
Author
Owner

@cwmohit commented on GitHub (Feb 12, 2024):

/attempt #877

<!-- gh-comment-id:1938475216 --> @cwmohit commented on GitHub (Feb 12, 2024): /attempt #877
Author
Owner

@ephraimduncan commented on GitHub (Sep 21, 2024):

Closing this issue as the signing pad is not currently available on the landing page.

<!-- gh-comment-id:2365336083 --> @ephraimduncan commented on GitHub (Sep 21, 2024): Closing this issue as the signing pad is not currently available on the landing page.
Sign in to join this conversation.
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#267
No description provided.