24

Did the grace period for edits on posts recently go away? Or did the mechanism break maybe?

I was recently editing an FAQ post on MSO, and after saving the edit, realized I changed something which I didn't intend to.

No problem, I noticed this well within the 5 minute grace period window; I edited again to fix the mistake. The edit summary from the previous edit appeared in the edit summary input below the post, I made my change and submitted it.

I checked the revision history of the post later, and noticed that my grace period edit had been logged as a separate edit, with the same edit summary as my prior edit.

No comments had been made on the post since the first edit, and none of the other criteria for invalidating the grace period appeared to apply.

For science, I tested this on a post of mine in the sandbox (all CW posts), and was able to replicate the behavior. I wasn't able to replicate this on a non-CW post was recently able to replicate this on Stack Overflow proper as well (first edit, non-CW post).

Here's another case from @bobble on a non-CW post here on MSE.

Did the editing grace period on posts break? Was it turned off intentionally?

This appears not to have the same underlying cause as this : All post history events are now incorrectly showing as edits in post histories and timelines after all, since that was officially fixed, but I'm still able to repro this on my sandbox post.

Improve this question
4
  • 1
    The same thing happened to me when I was improving a suggested edit from the review queue: ell.stackexchange.com/posts/183735/revisions It kept the comment, so I thought there would be one revision, but nope.
    – ColleenV
    Commented Sep 14, 2021 at 20:00
  • 5
    My guess is that it's related to this bug: meta.stackexchange.com/q/369846/334566
    – PM 2Ring
    Commented Sep 14, 2021 at 20:38
  • 1
    @PM2Ring true, as the developer mentioned in a comment, the bug has wider scope than reported there and it broke many things.
    – Shadow Wizard
    Commented Sep 15, 2021 at 8:05
  • 2
    @PM2Ring That was a great guess, but it appears this is not the case; the other bug is marked as complete and was deployed, but I'm still able to repro this one.
    – zcoop98
    Commented Sep 15, 2021 at 20:54

1 Answer 1

Reset to default
17

This bug was related to the bug that we fixed yesterday. We got the grace period fixed this evening (and actually, the fix for this bug was the same as the fix for this one). It should be live soon (within a half hour or so). Thank you so much for reporting it.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .