Comment drafts are lost when navigating away #2426

Closed
opened 2026-03-22 14:07:07 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @Brianmitchtay on GitHub (Nov 24, 2025).

Description

When typing a comment on a task, if I accidentally navigate away from the page before saving the comment, the draft text is completely lost. I have lost lots of work this way and it's extremely frustrating. The comment field does not retain unsaved draft content.

Expected Behavior

Ideally comment drafts should be automatically saved (either to localStorage or similar) for a time so that if the page is left on accident etc., the draft text is preserved when returning to the task.

Steps to Reproduce

  1. Open a task
  2. Start typing a comment (but do not click Save)
  3. Navigate to a different task or page
  4. Return to the same task
  5. The comment field is empty - the draft text is gone

Vikunja Version

v0.24.6

Browser and version

AFAIK this happens across all browsers.

Can you reproduce the bug on the Vikunja demo site?

Yes

Which alternatives did you consider using instead?

Didn't really consider building something else as this seems like it can probably be solved easily in the app.

Originally created by @Brianmitchtay on GitHub (Nov 24, 2025). ### Description When typing a comment on a task, if I accidentally navigate away from the page before saving the comment, the draft text is completely lost. I have lost lots of work this way and it's extremely frustrating. The comment field does not retain unsaved draft content. ### Expected Behavior Ideally comment drafts should be automatically saved (either to localStorage or similar) for a time so that if the page is left on accident etc., the draft text is preserved when returning to the task. ### Steps to Reproduce 1. Open a task 2. Start typing a comment (but do not click Save) 3. Navigate to a different task or page 4. Return to the same task 5. The comment field is empty - the draft text is gone ### Vikunja Version v0.24.6 ### Browser and version AFAIK this happens across all browsers. ### Can you reproduce the bug on the Vikunja demo site? Yes ### Which alternatives did you consider using instead? Didn't really consider building something else as this seems like it can probably be solved easily in the app.
Author
Owner

@Brianmitchtay commented on GitHub (Nov 24, 2025):

First issue I've ever opened with y'all so please excuse any missing information. I've vibe-coded a solution for this that appears to work, but imagine it could be better built by a proper dev

@Brianmitchtay commented on GitHub (Nov 24, 2025): First issue I've ever opened with y'all so please excuse any missing information. I've vibe-coded a solution for this that appears to work, but imagine it could be better built by a proper dev
Author
Owner

@vikunja-bot-app[bot] commented on GitHub (Nov 24, 2025):

This issue has been fixed in #1868, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Nov 24, 2025): This issue has been fixed in #1868, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Author
Owner

@Brianmitchtay commented on GitHub (Nov 25, 2025):

Works great for me! Thanks so much for the fix @kolaente 🫶

@Brianmitchtay commented on GitHub (Nov 25, 2025): Works great for me! Thanks so much for the fix @kolaente 🫶
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2426