-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logged out while editing #11797
Comments
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
bump |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
Does this really still happen with the notification event stream? |
If you edit an issue and keep it open in a tab for some time, your session may end. But if you click "save", there is no indication of an error at all, despite your changes not being saved! Only upon reloading the page you will be redirected to the login screen, with all your changes being irrecoverably lost. Especially with larger edits, this is quite frustrating.
I understand that mitigating this completely is complex (eg maintaining an edit log/drafts in the browser's localStorage would be a way), but the least gitea could do would be a show of an error message instead of pretending that changes have been saved correctly.
The text was updated successfully, but these errors were encountered: