starred/documenso

Fork 0

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

[GH-ISSUE #907] [Improvement] Fields should not be able to stack exactly on top of each other #281

New issue

Open

opened 2026-02-26 18:46:17 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @sumitbishti on GitHub (Feb 5, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/907

Originally assigned to: @sumitbishti on GitHub.

Describe the improvement you are suggesting in detail

Fields should have some area exclusively for themself. So that they can be clicked by the signer. Right now if the Sender stack all the fields exactly on top of each other, the Recipient can only click on the top most field.

All the fields are stacked on top of each other in the below img

Additional Information & Alternatives (optional)

No response

Do you want to work on this improvement?

Yes

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 @sumitbishti on GitHub (Feb 5, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/907 Originally assigned to: @sumitbishti on GitHub. ### Describe the improvement you are suggesting in detail Fields should have some area exclusively for themself. So that they can be clicked by the signer. Right now if the Sender stack all the fields exactly on top of each other, the Recipient can only click on the top most field. All the fields are stacked on top of each other in the below img <img width="560" alt="image" src="https://github.com/documenso/documenso/assets/75713174/67b063ca-80a8-4470-9187-8951f9a854a6"> ### Additional Information & Alternatives (optional) _No response_ ### Do you want to work on this improvement? Yes ### 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:17 +03:00

kerem commented

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

Author

Owner

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

Fields should have some area exclusively for themself

How are you intending to resolve this? Making it so fields can't be placed on top of each other?

I think we should be updating the layering so that inserted fields are behind uninserted fields

@dguyen commented on GitHub (Feb 6, 2024): > Fields should have some area exclusively for themself How are you intending to resolve this? Making it so fields can't be placed on top of each other? I think we should be updating the layering so that inserted fields are behind uninserted fields

kerem commented

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

Author

Owner

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

I will have to think about it first. Will let you know.

@sumitbishti commented on GitHub (Feb 6, 2024): I will have to think about it first. Will let you know.

kerem commented

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

Author

Owner

@Mythie commented on GitHub (Feb 7, 2024):

While I can't think of any good reasons to not place fields on top of eachother I can imagine users getting frustrated if they attempt to drop a field and it only just intersects with another one by a few pixels (name + date) which causes the drop to fail.

@Mythie commented on GitHub (Feb 7, 2024): While I can't think of any good reasons to not place fields on top of eachother I can imagine users getting frustrated if they attempt to drop a field and it only just intersects with another one by a few pixels (name + date) which causes the drop to fail.

kerem commented

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

Author

Owner

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

While I can't think of any good reasons to not place fields on top of eachother

If you do place, how a signer is supposed to fill the fields that are below the top most one? Which do not have any area to click on.

I think we should only allow a minimum of 50% percent of a field's area to be intersected by other fields.

@sumitbishti commented on GitHub (Feb 8, 2024): > While I can't think of any good reasons to not place fields on top of eachother If you do place, how a signer is supposed to fill the fields that are below the top most one? Which do not have any area to click on. I think we should only allow a minimum of 50% percent of a field's area to be intersected by other fields.

kerem commented

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

Author

Owner

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

Lucas is right; failing drops would be frustrating
If we do this, it would have to be a "physical limitation" that you can drag them overlapping
Though, I have never seen this limited before, I assume it not because a lot of docs have tiny space and this would hinder things
happy to try out a version of the physical block, but no guarantees we merge it

@ElTimuro commented on GitHub (Feb 8, 2024): - Lucas is right; failing drops would be frustrating - If we do this, it would have to be a "physical limitation" that you can drag them overlapping - Though, I have never seen this limited before, I assume it not because a lot of docs have tiny space and this would hinder things - happy to try out a version of the physical block, but no guarantees we merge it

kerem commented

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

Author

Owner

@ameeetgaikwad commented on GitHub (Jan 10, 2025):

Is someone working on this?

@ameeetgaikwad commented on GitHub (Jan 10, 2025): Is someone working on this?

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

No description provided.

Rows
Columns