Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Saved text not cleared when posted

Post

Saved text not cleared when posted

+4
−0

Over the last couple years or so, I've occasionally come back to a question where I posted an answer, and the system popped me into the post editor as if I had unsaved changes. This is now happening pretty much every time.

Just a few minutes ago, I posted an answer to https://meta.codidact.com/posts/293942. I was left in the post editor immediately after posting, even though I could see the answer was posted. This time I noticed a typo, so fixed it, and posted the revised version. Instead of updating the original post, it created a second one. I had to manually cancel out of the post editor, then delete the first answer.

There are a number of questions that report this bug or something that seems closely related:

  1. clearing draft after clicking "Save Post in Q&A"

    The most direct description of the problem, but that is closed so I couldn't add to it.

  2. "Remember last post edit in process" not clearing automatically

    The question #1 is supposedly a duplicate of. The description is much less clear, and the bug claims to be fixed.

  3. Saving post after ALT text warning still treats the draft as unsaved

    I think is ultimately the same bug, but is confusing and hard to search for because it focuses on alt-text of images.

  4. Draft not discarded after posting an answer

    A good description of the problem I didn't find when writing my question here. It was pointed out in a comment. My question could be closed as a duplicate of this one.

  5. Draft of previous edit (including edit comment) loaded for new edit

    Probably the same underlying bug, linked to from #4.

Added

Posting this question did NOT exhibit the behavior. The bug might be limited to answers or maybe it's just random.

Another incident, 14 May 2025

It just happened to me again. I posted my answer to a question that already had one existing answer. I could see my answer get correctly posted, but then immediately below that my text was shown in the post editor, and the following banner was below that:

I cancelled out of that edit session, and everything seemed correct after that.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

more reports (2 comments)
Another question for your list of times the bug has been raised (3 comments)
Another question for your list of times the bug has been raised
trichoplax‭ wrote 22 days ago

I raised Draft not discarded after posting an answer a few months ago, and it was pointed out that it had been raised previously, and fixed in 2021, but it appeared to be broken again. There are comments there showing it is also happening to others.

I haven't closed your question as a duplicate because it covers several different questions that might not all be the same problem, so it seems a good summary of what needs to be investigated.

Olin Lathrop‭ wrote 21 days ago

I thought there was a better question addressing this problem, but couldn't find it when searching. I think your question should be the official version of this bug report. Mine and possibly others should be closed pointing to yours, but add links to all the questions reporting this bug to your question. That way when someone finds any of these questions by searching, they'll find yours, and can from there find all the other instances where this bug was reported, each one possibly with different details.

trichoplax‭ wrote 21 days ago

I've already linked in both directions between this post and that post (here in the comments and there in the question body). That indirectly links that one to all the posts you found, so hopefully whatever fix is implemented can be checked against all of those too.