Bug 481088 - Neochat Doesn't remember scroll position
Summary: Neochat Doesn't remember scroll position
Status: RESOLVED DUPLICATE of bug 476291
Alias: None
Product: NeoChat
Classification: Applications
Component: General (other bugs)
Version First Reported In: 23.08.4
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-08 22:14 UTC by Shawn W Dunn
Modified: 2024-02-29 21:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn W Dunn 2024-02-08 22:14:40 UTC
SUMMARY
When Switching between Channels, Neochat seems to pick a position in the channel at random, some point in the past, it doesn't *seem* to be consistent.


STEPS TO REPRODUCE
1. Switch from one Channel to another in Neochat, that is indicating there are "new messages"
2. 

OBSERVED RESULT
When the "new" channel loads, the scroll position is the previous day at 15:21
Switch back to the previous channel, the scroll position is at the newest post in that channel
Switch back to the "new" channel, and now the scroll position is at the previous day, at 15:15

EXPECTED RESULT
The "new" channel would load either at the "last read message", "first unread message" or the most recent message in that channel.   Any of the three behaviors would be acceptable.

SOFTWARE/OS VERSIONS 
Linux/KDE Plasma:  openSUSE Kalpa (Linux 6.7.2) Wayland
(available in About System)
KDE Plasma Version:  5.27.10
KDE Frameworks Version: 5.114.0
Qt Version:  5.15.12

ADDITIONAL INFORMATION
Comment 1 Tammes Burghard 2024-02-09 16:47:13 UTC
This looks related to https://bugs.kde.org/show_bug.cgi?id=476291, but with a bit more nuance to it, so I will not mark it as duplicate and leave that decision to others.
Comment 2 Tammes Burghard 2024-02-09 17:00:03 UTC
I just tested this on plasma 6 and it always opens chats at the most recent message. So I guess this might be fixed there?
Comment 3 Shawn W Dunn 2024-02-09 17:04:34 UTC
Entirely possible, I've not yet tested on Plasma6, and if the Plasma6 upgrade is what fixes it, that certainly is fine by me, let me try it, and see what happens.
Comment 4 James Graham 2024-02-19 20:04:15 UTC

*** This bug has been marked as a duplicate of bug 476291 ***