When I delete a thread with, e.g. N msgs: select first message, shift-click on last msg in thread, the next msg below the thread gets selected. Now go down e.g. 2xN msg and select them again with shift-click. Now only the first message is select, the next N-1 msg are not selected, the last N msg are selected again. IMHO that a bug, I would expect that all 2xN msg are selected. Workaround is after delete of the thread, click once on the first msg after the thread that is already automaticly selected, then the following shift-click selects all msg in the range as expected by a shift-click Reproducible: Always Steps to Reproduce: 1. Open a folder and expand a thread (that has N msgs) 2. Click on the 1st msg of the thread 3. Shift-Click at the last thread msg and delete the thread (next msg after thread is automaticly selected 4. Scroll down lets say 2xN msg and shift-click on this msg again. Actual Results: * 1st msg, that is automaticly selected the delete is still selected * the next N-1 msg are not selected * the last N msg are selected Expected Results: All 2xN msg are selected from 1st automaticly selected msg to the last msg that I shift-clicked. Message list setup: Msg sort order: By date/time of most recent in subtree Msg sort direction: Most recent on top Group sort direction: decending Aggregation: Current Activity, Threaded Theme: fancy
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.
I can't reproduce the bug, that I've reported, with kmail2 5.1.3 anymore. Therefore I'll close the bug.