Updated text lost on Save when editing existing issue #8719

New Issue

GiteaMirror · 2025-11-02T08:15:31-06:00

GiteaMirror commented

2025-11-02 08:15:31 -06:00

Originally created by @aschrijver on GitHub (Mar 18, 2022).

Gitea Version

1.16.4+35-gafe98af

Git Version

No response

Operating System

No response

How are you running Gitea?

This issue refers to Gitea as run on Codeberg where I am user 'circlebuilder'.

Database

No response

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

Occurrence: The issue I am reporting I have now experienced a total of about 4 times, but I cannot reproduce it unfortunately. Always takes me off guard.

Background: In various repo's on Codeberg I regularly update existing issues by adding additional information to them by clicking 'Edit'. They contain nothing special, just markdown and regular English text. I feel the bug occurs when on issues that already contain longer text amount (say ~2 full pages of printed text), and likely also when adding more than just a single bullet point to a list.

Bug: I click edit and at the bottom of the text add a bunch of additions. Often bullet-formatted. Between editing I switch browser tabs (Firefox 96.0 on Ubuntu) and copy/paste plain text. When done I click 'Save' and ... the issue is in its old state before I started editing. The text is lost, and no error message is shown.

Until now every time I was aghast and pushed the browser's Back button in hopes it would bring back the issue form in edit mode (as what Github does), but Gitea doesn't support that and leads back to the issue list. So I have to type anew (though now I've come to conclusion that I should really use different tools than Gitea as the current work method is too unreliable).

Issue happened just now, but in a private repo, so I cannot include the URL. Note that other times I experienced this it was on older version than current 1.16 release.

Screenshots

No response

Originally created by @aschrijver on GitHub (Mar 18, 2022). ### Gitea Version 1.16.4+35-gafe98af ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? This issue refers to Gitea as run on [Codeberg](https://codeberg.org) where I am user 'circlebuilder'. ### Database _No response_ ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description **Occurrence**: The issue I am reporting I have now experienced a total of about 4 times, but I cannot reproduce it unfortunately. Always takes me off guard. **Background**: In various repo's on Codeberg I regularly update existing issues by adding additional information to them by clicking 'Edit'. They contain nothing special, just markdown and regular English text. I feel the bug occurs when on issues that already contain longer text amount (say ~2 full pages of printed text), and likely also when adding more than just a single bullet point to a list. **Bug**: I click edit and at the bottom of the text add a bunch of additions. Often bullet-formatted. Between editing I switch browser tabs (Firefox 96.0 on Ubuntu) and copy/paste plain text. When done I click 'Save' and ... the issue is in its old state before I started editing. The text is lost, and no error message is shown. Until now every time I was aghast and pushed the browser's Back button in hopes it would bring back the issue form in edit mode (as what Github does), but Gitea doesn't support that and leads back to the issue list. So I have to type anew (though now I've come to conclusion that I should really use different tools than Gitea as the current work method is too unreliable). Issue happened just now, but in a private repo, so I cannot include the URL. Note that other times I experienced this it was on older version than current 1.16 release. ### Screenshots _No response_

GiteaMirror added the topic/ui-interaction type/bug labels 2025-11-02 08:15:31 -06:00

GiteaMirror closed this issue

2025-11-02 08:15:31 -06:00

GiteaMirror commented

2025-11-02 08:15:32 -06:00

@aschrijver commented on GitHub (Mar 19, 2022):

@fnetX on the related Codeberg issue pointed out that this is likely the CSRF token that expires, as reported in #17850 and in this case not gracefully handled.

I don't know the expiration timeout, but I was indeed having the issue in Edit-mode for more than just a couple of secs. Maybe half an hour.

@aschrijver commented on GitHub (Mar 19, 2022): @fnetX on [the related Codeberg issue](https://codeberg.org/Codeberg/Community/issues/600) pointed out that this is likely the CSRF token that expires, as reported in #17850 and in this case not gracefully handled. I don't know the expiration timeout, but I was indeed having the issue in Edit-mode for more than just a couple of secs. Maybe half an hour.

GiteaMirror commented

2025-11-02 08:15:32 -06:00

@wxiaoguang commented on GitHub (Apr 6, 2022):

More details: