starred/documenso

Fork 0

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

[GH-ISSUE #2335] DocumentShareButton dialog immediately closes when triggered from DropdownMenu #660

New issue

Open

opened 2026-02-26 18:47:57 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @mKoonrad on GitHub (Dec 17, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2335

Issue Description

DocumentShareButton component, when used as a DropdownMenuItem trigger, fails to remain open. When a user clicks "Share Signing Card" option within the document action dropdown, the dialog appears for a split second and then immediately closes.

https://github.com/user-attachments/assets/967290a6-3d51-486d-b6ea-d3d26ec41ba5

Additionally, I suggest to change
github.com/documenso/documenso@df678d7d69/packages/ui/components/document/document-share-button.tsx (L141-L143)
to

<DialogTitle class="break-words text-lg font-semibold">

to avoid this window on some languages with longer translation.

With

<DialogTitle">

With

<DialogTitle class="break-words text-lg font-semibold">

Steps to Reproduce

Go to the documents list
Click on the "More" (three dots) icon.
Click on "Share Signing Card".
Observe that dialog flashes briefly and disappears.

Expected Behavior

Sharing dialog should remain open after being triggered from the dropdown menu.

Current Behavior

The dialog is forcefully closed immediately after opening.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

v2.3.0

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 @mKoonrad on GitHub (Dec 17, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2335 ### Issue Description DocumentShareButton component, when used as a DropdownMenuItem trigger, fails to remain open. When a user clicks "Share Signing Card" option within the document action dropdown, the dialog appears for a split second and then immediately closes. https://github.com/user-attachments/assets/967290a6-3d51-486d-b6ea-d3d26ec41ba5 Additionally, I suggest to change https://github.com/documenso/documenso/blob/df678d7d69c4019f9d140963702ea012a7203681/packages/ui/components/document/document-share-button.tsx#L141-L143 to ``` <DialogTitle class="break-words text-lg font-semibold"> ``` to avoid this window on some languages with longer translation. With ``` <DialogTitle"> ``` <img width="961" height="1066" alt="Image" src="https://github.com/user-attachments/assets/200d5af8-ce55-475e-bb1c-a08d99bb7ee0" /> With ``` <DialogTitle class="break-words text-lg font-semibold"> ``` <img width="880" height="1071" alt="Image" src="https://github.com/user-attachments/assets/51b927e3-a337-4cf3-99ba-2a08053aef22" /> ### Steps to Reproduce 1. Go to the documents list 2. Click on the "More" (three dots) icon. 3. Click on "Share Signing Card". 4. Observe that dialog flashes briefly and disappears. ### Expected Behavior Sharing dialog should remain open after being triggered from the dropdown menu. ### Current Behavior The dialog is forcefully closed immediately after opening. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] v2.3.0 ### 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 added the

status: triage

label

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

kerem commented

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

Author

Owner

@coderabbitai[bot] commented on GitHub (Dec 17, 2025):

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

Create Plan

Examples

_{You can configure auto-planning by selecting labels in the issue_enrichment configuration.}

🔗 Similar Issues

Related Issues

documenso/documenso#1139 - feat: force signature fields for document signers [merged]
documenso/documenso#1162 - fix: truncation of titles to fix UI breaks [merged]
documenso/documenso#1334 - fix: select field ux [merged]
documenso/documenso#1412 - fix: close direct link dialog when you click on save [merged]
documenso/documenso#1449 - feat: add signing link copy [merged]

👤 Suggested Assignees

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

@coderabbitai[bot] commented on GitHub (Dec 17, 2025):  ## 📝 CodeRabbit Plan Mode Generate an implementation plan and prompts that you can use with your favorite coding agent. - [ ]  Create Plan <details> <summary>Examples</summary> - [Example 1](https://github.com/coderabbitai/git-worktree-runner/issues/29#issuecomment-3589134556) - [Example 2](https://github.com/coderabbitai/git-worktree-runner/issues/12#issuecomment-3606665167) </details> <sub>You can configure auto-planning by selecting labels in the issue_enrichment configuration.</sub> ## 🔗 Similar Issues **Related Issues** - https://github.com/documenso/documenso/issues/2216 - https://github.com/documenso/documenso/issues/1503 - https://github.com/documenso/documenso/issues/2100 - https://github.com/documenso/documenso/issues/1464 - https://github.com/documenso/documenso/issues/2132 ## 🔗 Related PRs documenso/documenso#1139 - feat: force signature fields for document signers [merged] documenso/documenso#1162 - fix: truncation of titles to fix UI breaks [merged] documenso/documenso#1334 - fix: select field ux [merged] documenso/documenso#1412 - fix: close direct link dialog when you click on save [merged] documenso/documenso#1449 - feat: add signing link copy [merged] ## 👤 Suggested Assignees - [mKoonrad](https://github.com/mKoonrad) - [catalinpit](https://github.com/catalinpit) - [daKmoR](https://github.com/daKmoR) - [mogomm](https://github.com/mogomm) - [billsinc](https://github.com/billsinc) --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit) or [schedule a call](https://calendly.com/parth-coderabbit/issues-feedback)!

kerem commented

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

Author

Owner

@tonypartridge commented on GitHub (Dec 22, 2025):

Same here, Also the share url redirects to docuseal.com even if using shelf hosted.

@tonypartridge commented on GitHub (Dec 22, 2025): Same here, Also the share url redirects to docuseal.com even if using shelf hosted.

kerem commented

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

Author

Owner

@aditya-chakraborty commented on GitHub (Jan 21, 2026):

Hi @ephraimduncan @Mythie can I work on this issue please?

@aditya-chakraborty commented on GitHub (Jan 21, 2026): Hi @ephraimduncan @Mythie can I work on this issue please?

kerem commented

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

Author

Owner

@mKoonrad commented on GitHub (Jan 22, 2026):

@aditya-chakraborty I'm not a member of Documenso team, but based on their usual activity here, it’s usually best to just go ahead and open PR :)

@mKoonrad commented on GitHub (Jan 22, 2026): @aditya-chakraborty I'm not a member of Documenso team, but based on their usual activity here, it’s usually best to just go ahead and open PR :)

kerem referenced this issue

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

[PR #663] [MERGED] feat: add/update title of the Document #1108

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

No description provided.

Rows
Columns