When loading new posts don't jump to the newest post or otherwise lose my place in the timeline. #300
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#300
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea
I usually start reading the oldest unread message (which I have to search for) and then I scroll up until I have read all the unread posts. Then if I click the "Show New" button, it jumps to the top and I lose my place, and have to scroll back down to try to find the last message I read, which is time consuming and annoying.
Is there any way to just have to stay on the last message I read so I can continue to scroll up? If there are people who like the existing behavior ten maybe this could be made an option.
For that matter, what I would personally really prefer is an option to show the OLDEST message at the top and then scroll down to read the newer ones, but with a way to start where you left off reading. But that would require the web client to keep track of what you have already read so that may not be possible or easily doable. But in any case I would very much like it if you could make it not jump to the newest post after a reload.
I should add that as far as I know this is a frontend issue but I am not a programmer so I might be wrong about that, if so I apologize.
The reasoning
Because the current method makes it difficult to follow your home timeline in chronological order, because every time you load new messages it jumps away from the last message you read.
Have you searched for this feature request?
In theory this should be already implemented in the back-end side with Markers. It would only be a matter of designing an intuitive way of "saving" and "loading", or to make it behind-the-scenes. Mergan's been meaning to do this one as well, since I too search for the last unread message and read chronologically