Bug 504624 - SMS message pane never starts out at last message, and scrolling is very broken.
Summary: SMS message pane never starts out at last message, and scrolling is very broken.
Status: RESOLVED DUPLICATE of bug 477361
Alias: None
Product: kdeconnect
Classification: Applications
Component: messaging-application (other bugs)
Version First Reported In: 25.04.1
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Simon Redman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-21 16:42 UTC by Ian Kidd
Modified: 2025-07-22 20:59 UTC (History)
1 user (show)

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


Attachments
Clip of scrolling behaviour (343.29 KB, video/webm)
2025-05-21 16:42 UTC, Ian Kidd
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Kidd 2025-05-21 16:42:54 UTC
Created attachment 181618 [details]
Clip of scrolling behaviour

I've noticed this on virtually every machine I've used KDE Connect's SMS pane on for a long time.  It doesn't seem version or distro specific.

When you click on a message thread from the left, it opens the messages in the pane on the right somewhere above the last message.  If you scrollwheel down to the bottom, it jitters as you scroll until it seems like it takes up enough slack to actually start scrolling towards the bottom.  When you reach the current last message, you'll notice the scroll bar slider is some distance from the bottom.  If you grab the slider bar and slide it right to the bottom, it'll scroll the last message almost off the top of the pane.

I'm happy to help troubleshoot this with anyone that wants to work with me, though I might need some instructions to install test versions.
Comment 1 dzvanhoffen 2025-07-17 00:24:28 UTC
Getting the same issue, makes it completely unusable when using a trackpad. It always jitters to the top and doesn't let me scroll down at all. I can't even seem to grab the scrollbar. Happy to try and help if you need more info
Comment 2 Simon Redman 2025-07-22 20:59:25 UTC
Thank you for taking the time to report this. It seems to be a duplicate, so I will close this bug in favour of the older one.

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