[GH-ISSUE #886] Field Sizing

kerem commented

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

Owner

Originally created by @ElTimuro on GitHub (Jan 30, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/886

Originally assigned to: @hkrhemendra on GitHub.

Describe the improvement you are suggesting in detail

Signature and other fields below a certain size don't make sense
The value placeholder should be respected by the minimum size
An absolute minimum size needs to be defined
They may be even bad pattern because hard to see

Additional Information & Alternatives (optional)

No real alternative, just letting the size adjustable completely free can lead to some not so nice/ hard to hit fields

Do you want to work on this improvement?

No

Please check the boxes that apply to this improvement suggestion.

I have searched the existing issues and improvement suggestions to avoid duplication.
I have provided a clear description of the improvement being suggested.
I have explained the rationale behind this improvement.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.

Originally created by @ElTimuro on GitHub (Jan 30, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/886 Originally assigned to: @hkrhemendra on GitHub. ### Describe the improvement you are suggesting in detail - Signature and other fields below a certain size don't make sense - The value placeholder should be respected by the minimum size - An absolute minimum size needs to be defined - They may be even bad pattern because hard to see ### Additional Information & Alternatives (optional) - No real alternative, just letting the size adjustable completely free can lead to some not so nice/ hard to hit fields ### Do you want to work on this improvement? No ### Please check the boxes that apply to this improvement suggestion. - [X] I have searched the existing issues and improvement suggestions to avoid duplication. - [X] I have provided a clear description of the improvement being suggested. - [X] I have explained the rationale behind this improvement. - [X] I have included any relevant technical details or design suggestions. - [X] I understand that this is a suggestion and that there is no guarantee of implementation.

kerem added the

labels

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

kerem commented

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

Author

Owner

@FatumaA commented on GitHub (Jan 30, 2024):

I'd like to pick this up

@FatumaA commented on GitHub (Jan 30, 2024): I'd like to pick this up

kerem commented

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

Author

Owner

@newtronahmed commented on GitHub (Jan 30, 2024):

Am interested in taking this on

@newtronahmed commented on GitHub (Jan 30, 2024): Am interested in taking this on

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Jan 30, 2024):

@FatumaA I'll be assigning this to you since you were the first

@ephraimduncan commented on GitHub (Jan 30, 2024): @FatumaA I'll be assigning this to you since you were the first

kerem commented

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

Author

Owner

@FatumaA commented on GitHub (Feb 6, 2024):

Hi @dephraiim,
I took a look here and I'm stuck on actually finding the right part of the codebase.
So far, it seems the fields under app/(Signing) are the fields that are displayed after the document is made and sent. But we want to get to the fields as they are being added to the document to restrict their size.

I hope this makes sense and I'd appreciate some help on this

@FatumaA commented on GitHub (Feb 6, 2024): Hi @dephraiim, I took a look here and I'm stuck on actually finding the right part of the codebase. So far, it seems the fields under app/(Signing) are the fields that are displayed after the document is made and sent. But we want to get to the fields as they are being added to the document to restrict their size. I hope this makes sense and I'd appreciate some help on this

kerem commented

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

Author

Owner

@sokhuong-uon commented on GitHub (Apr 1, 2024):

I see these lines trying to use minWidth and minHeight.
github.com/documenso/documenso@cbe6270494/packages/ui/primitives/document-flow/field-item.tsx (L100-L101)
Is there any problem with using fixed pixel values for minWidth and minHeight?

minHeight={'20px'}
minWidth={'60px'}

I tried zooming the document and didn't face any issues tho.

@sokhuong-uon commented on GitHub (Apr 1, 2024): I see these lines trying to use minWidth and minHeight. https://github.com/documenso/documenso/blob/cbe62704940ee0877f62a417c078db855c9c9fe7/packages/ui/primitives/document-flow/field-item.tsx#L100-L101 Is there any problem with using fixed pixel values for minWidth and minHeight? ```ts minHeight={'20px'} minWidth={'60px'} ``` I tried zooming the document and didn't face any issues tho.

kerem commented

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

Author

Owner

@hkrhemendra commented on GitHub (Jul 2, 2024):

Hi, I am looking for my first contribution to open source.
Can I pick this issue?

@hkrhemendra commented on GitHub (Jul 2, 2024): Hi, I am looking for my first contribution to open source. Can I pick this issue?

kerem commented

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

Author

Owner

@FatumaA commented on GitHub (Jul 2, 2024):

Should be fine if it's still an issue, right @ephraimduncan?

@FatumaA commented on GitHub (Jul 2, 2024): Should be fine if it's still an issue, right @ephraimduncan?

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Jul 3, 2024):

Hi @hkrhemendra, I'm going to assign this to you

@ephraimduncan commented on GitHub (Jul 3, 2024): Hi @hkrhemendra, I'm going to assign this to you

kerem commented

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

Author

Owner

@hkrhemendra commented on GitHub (Jul 3, 2024):

Hi @ephraimduncan @FatumaA, I have checked the signature field and I am not facing any issue.
Can you share me a screenshot? So, that I can check at the correction location of issue.
I am attaching the screenshot where I have checked the issue.

@hkrhemendra commented on GitHub (Jul 3, 2024): Hi @ephraimduncan @FatumaA, I have checked the signature field and I am not facing any issue. Can you share me a screenshot? So, that I can check at the correction location of issue. I am attaching the screenshot where I have checked the issue. ![Screenshot 2024-07-03 at 8 50 19 PM](https://github.com/documenso/documenso/assets/51264979/029f9cb8-761e-4c09-beab-2ae014f9b2b3)

kerem commented

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

Author

Owner

@apsinghdev commented on GitHub (Aug 20, 2024):

hey @ephraimduncan I found this issue is yet to be fixed. can I work on this issue?

@apsinghdev commented on GitHub (Aug 20, 2024): hey @ephraimduncan I found this issue is yet to be fixed. can I work on this issue?

kerem commented

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

Author

Owner

@asxzy commented on GitHub (Aug 29, 2024):

The field size is fixed and can be very annoying to show in a document.

@asxzy commented on GitHub (Aug 29, 2024): The field size is fixed and can be very annoying to show in a document. <img width="538" alt="image" src="https://github.com/user-attachments/assets/adfe7b7e-8598-4193-b052-ff43b1ecbc17">

kerem commented

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

Author

Owner

@ElTimuro commented on GitHub (Sep 5, 2024):

@asxzy we already have plans to address this and will post updates here.
The plan is to let it scale linearly and not limiting the content, just will take a bit to do right

@ElTimuro commented on GitHub (Sep 5, 2024): - @asxzy we already have plans to address this and will post updates here. - The plan is to let it scale linearly and not limiting the content, just will take a bit to do right

kerem commented

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

Author

Owner

@apsinghdev commented on GitHub (Sep 6, 2024):

@ElTimuro To my knowledge, there are a total of 10 fields, I guess, applying the idea of field sizing won't be suitable for some fields like Radio, Checkbox, Dropdown, Date, so do you have an explicit list of the one's that need this functionality? Please feel free to correct me if I'm wrong.

@apsinghdev commented on GitHub (Sep 6, 2024): @ElTimuro To my knowledge, there are a total of 10 fields, I guess, applying the idea of field sizing won't be suitable for some fields like `Radio`, `Checkbox`, `Dropdown`, `Date`, so do you have an explicit list of the one's that need this functionality? Please feel free to correct me if I'm wrong.

kerem commented

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

Author

Owner

@rohitmore07 commented on GitHub (Feb 13, 2025):

Hey @ephraimduncan, I am very keen to work on this issue . I would be really happy if you could assign this issue to me.

@rohitmore07 commented on GitHub (Feb 13, 2025): Hey @ephraimduncan, I am very keen to work on this issue . I would be really happy if you could assign this issue to me.

kerem referenced this issue

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

[PR #269] [MERGED] fix: [DOC-296] Add changesets for automatic release versioning #837

Rows
Columns

[GH-ISSUE #886] Field Sizing #268

Describe the improvement you are suggesting in detail

Additional Information & Alternatives (optional)

Do you want to work on this improvement?

Please check the boxes that apply to this improvement suggestion.