Bug 321941 - the message highlighted in a list isn't necessarily the anchor for shift-click selection
Summary: the message highlighted in a list isn't necessarily the anchor for shift-clic...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-04 09:16 UTC by yuzyk
Modified: 2017-01-07 21:36 UTC (History)
0 users

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 yuzyk 2013-07-04 09:16:21 UTC
Because KMail2 is still pretty crappy, I've had A LOT of duplicate mails populating folders from akonadi or filtering or who-knows-what. I've had to delete a lot of mails, and noticed that if I highlight and delete mails, the highlighted message isn't the anchor for a following shift-click selection. I sort my message list in descending Date order, so maybe that's part of the problem.

Reproducible: Always

Steps to Reproduce:
1. Have a bunch of messages to delete in a folder.
2. Highlight some, but not all, and delete them.
3. Scroll down and shift-click to select more messages
Actual Results:  
The selection does not extend from the highlighted message to the shift-clicked message.

Expected Results:  
The selection should extend from the highlighted message to the shift-clicked message.

I sort messages in descending Date order.
Comment 1 Denis Kurz 2016-09-24 18:18:35 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:36:05 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.