(Boosts appreciated.)

Short story: My pull request for solving the GUI scrolling problem in Slow mode needs some support. Some thumbs up on the request is probably all it needs. If you have a GitHub account, it should be easy to do. Note that I'm not asking anyone to create an account *just for this*.

Here it is:

https://github.com/mastodon/mastodon/pull/26380

Long story: Once upon a time, a newbie #Mastodon user complained about the fire hose of posts that was aimed at his face when he looked at the local and federated timelines on some server. Someone suggested using "Slow mode." In this mode, the *new* posts are loaded only when the user clicks on a "x new items" button.

This user was happy, for a while.

Eventually, he discovered that the "x new items" button would forget where he was in his timeline, and then he'd have to *manually* hunt for the last post he had read, and read from that point on.

This made him unhappy. Probably his #ActuallyAutistic mind was at play...

Note that the problem with the button is sometimes difficult to spot. In this user's experience, the GUI behaves fine at first, but eventually it loses the plot, and starts misbehaving, like a petulant child.

The pull request above aims to solve the problem. It remembers the topmost post you were looking at before pressing the button, and goes back to this. (When you have a "x new items" button, you don't even have to compute this, you could take a shortcut, but my solution also aims to deal with those buttons with ellipses that show up in the middle of the timeline. In this case, there is no shortcut that I can see.)

I'm running this code on my instance right now. I doubt that v4.1.6 will see a patch. I'm sure that v4.2.0 will NOT be released with my code. I doubt you'll see anything prior to v4.3.0.

(The user I mention in my story is me... in case anyone was still wondering.)

Oof... that was a long story.  

#PullRequest #GUI #misbehaving