My screen is too tall to interrupt reading a topic

[algorythmics]

When interrupting a topic and then coming back to it, the post that moves to the top of the screen is the post that was previously at the bottom of the screen. this is the worst. if you stopped reading quickly, or prefer the post you are reading to be towards the top of the screen, then discourse will remove that post from your consciousness for you on your return.

repro:
EDIT: I realized that since this repro is non-terminating, the devs may get into an infinite loop and potentially lose a large amount of time that could be spent on improving the software, as such I have amended it.

//1. go to any post
//2. scroll to half way through the post
//3. go to the topic listing
//4. click on the partially read post, DO NOT SCROLL.
//5. click on the topic listing.
//6. GOTO 4.

1. REPRO := False
2. go to any post
3. scroll to half way through the post
4. prevTopTopic := TopTopic
5. go to the topic listing
6. click on the partially read post, DO NOT SCROLL.
7. if(TopTopic != prevTopTopic)
8. REPRO := true
9. exit(0)
10. ELSE
11. click on the topic listing.
12. GOTO 6.

Expected Behaviour

Each return to the topic returns to the same location in the topic.

Actual Behaviour

Each return to the topic moves several posts later in the topic.

[algorythmics]

updated to prevent non-terminating discourse devs.

this is probably the 1 thread in the forum where discourse numbered list behaviour works in favour of the post writer, I was too lazy to update the numbers myself.

[Keith]

@algorythmics said:

updated to prevent non-terminating discourse devs.

They'll probably be stuck in the loop until their cache refreshes in 24 hours.

[Kuro]

@algorythmics said:

updated to prevent non-terminating discourse devs.

I dunno. Considering it's discourse we are talking about, they might be OOM after a minute or so. Not that much time lost, tbh.

Filed Under: You are clearly doing it wrong^tm by interupting your reading! Interuption is a barrier to reading!!!

[VinDuv]

@algorythmics said:

updated to prevent non-terminating discourse devs.

Your infinite loop was not very efficient anyway. Better do something like this:

Read this quote again.

[chubertdev]

WONT_FIX WORKING_AS_DESIGNED

Body is invalid; try to be a little more descriptive

[algorythmics]

@Matches im not sure if you are working through things and if so whether this will make things easier/harder. but the migration from discourse to a proper bug tracker is always going to be a pain to achieve I guess.

this still happens, and probably shouldnt

[Matches]

Yeah, I'll get here. Feel free to report it yourself and place the filed link here. Otherwise it's probably on the block for tonight since I'm going descending order.

[Yamikuronue]

Reported: https://bitbucket.org/masamunewos/discoursebugs/issue/37/returning-to-a-topic-does-not-position