게시글을 수정하면 이전 글로 돌아가는 문제 (다시)

Previously

Today I just edited post 135 in a thread and it took me back 20 posts (as previously reported) but the post number at the bottom said 134/135.

After editing I saw this:

Going to the bottom to see the post I was editing (135) showed this:

The post it showed me was actually 115:

1개의 좋아요

So to be clear what are the repro steps?

1개의 좋아요

Good question.

I’m still trying to reproduce it. Trying to remember if I did anything in particular during this edit.

A normal edit works OK.

1개의 좋아요

This is also happening when editing a DM in a long DM thread.

Ok, so what are the specific repro steps?

1개의 좋아요

The same as the old closed issue linked in the OP, but for DM view rather than Topic view.

1개의 좋아요

I’m also still seeing the original linked issue after editing a post. Same repro steps.

retrogameboards.com running 2.8.0beta2

Just confirming, this issue is specific to Safari iOS? Does not happen in Firefox / Chrome?

This is still happening BTW.

2개의 좋아요

I have experienced this as well, though I don’t have a specific repro.

4개의 좋아요

I’m still getting this. First reported in 2020.

Help me Obi-wan

1개의 좋아요

Still getting this.

It’s so annoying, like a scratch on a vinyl or CD that makes the audio skip back a bit. Then you have to find your place again.

Still happening :upside_down_face:

Hello!

Yes, this is still happening.

First reported November 2020.

2개의 좋아요

Hmm, could this be somehow related to:

Seems like a good chance

Unlikely, because the code for that bug was introduced after this one was first reported.

1개의 좋아요

I have a nagging bug for a long time when opening/closing topics that are assigned. It’s a much narrower use case, very much not what the report here is about, but there’s a slim chance the underlying issue is the same.

Here’s the PR for the other issue: DEV: Fix a rare bug where topic scrolls to OP unexpectedly by pmusaraj · Pull Request #34713 · discourse/discourse · GitHub, its repro steps are quite different, they’re related to the assign plugin (PR has specifics). But maybe, maybe… the fix can do something for your use case as well. One can always hope!

2개의 좋아요

There’s nothing I can do with this info. But I’m hopeful

1개의 좋아요

Anything I can do to help get this one licked?

It’s the final boss of bugs.

1개의 좋아요