Bug 477416

Summary:	Make the last read indicator act more like Konversation
Product:	[Applications] NeoChat	Reporter:	Marco Parillo <marco_parillo>
Component:	General	Assignee:	Tobias Fella <fella>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	carl, james.h.graham, jlp, josh
Priority:	NOR
Version First Reported In:	24.01.75
Target Milestone:	---
Platform:	Other
OS:	All
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marco Parillo 2023-11-23 12:17:33 UTC

SUMMARY
***
I rely on the last read indicator.
1. Could it be made more visible? I prefer bright red over what looks like just another bubble (even better if configurable)
2. It does not seem to show at all sometimes. Is that somehow related to the Matrix protocol?
3. Other times it seems to show after maybe 5-10 seconds. Again, Is that somehow related to the Matrix protocol?
4. Also, it seems to disappear quickly. Could it (again optionally would be even better) remain until some other relevent event?
5. Perhaps related, the up-arrow to indicate to jump to the first unread sometimes does not show, sometimes shows as I manually scroll up, and sometimes does not jump all the way, but only part of the way to my last read. Again, Is that somehow related to the Matrix protocol?
***


Operating System: KaOS (2023) 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.5.11-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
Memory: 15.0 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 5420

Comment 1 Tobias Fella 2023-11-24 13:12:10 UTC

I think some of those changes are reasonable for the compact mode. When using the bubbles, I'd prefer something closer to what we currently have

Comment 2 James Graham 2023-12-10 21:36:36 UTC

So for clarification for 2 and 3 you are pretty close in that what is shown is related to how matrix/libquotient works. When you open the room the last read message information is not always available. This means that even though we may have downloaded your last read message we haven't got the info from the server to tell us which message it is. We show the marker as soon as we get the info telling us which message it is.

For 5 the arrow isn't shown until the last read message has been downloaded, this means that it may appear as you scroll up because the message has been populated into the timeline above. That being said I've been thinking whether the behaviour should change to be always visible and scroll as high as possible when the last read message hasn't been loaded yet.