After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731278 - Next message is not selected after move
Next message is not selected after move
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-06-05 15:52 UTC by Adam Williamson
Modified: 2014-06-11 08:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Adam Williamson 2014-06-05 15:52:55 UTC
I believe this is since 3.12.2, but it may be 3.12. Running Fedora Rawhide, with evolution-3.12.2-1.fc21.x86_64 .

If I select the topmost message in any folder of my IMAPx account - I sort my mail with the most recent first, so that's the most recent message - and either mark it as "junk" (which, with my configuration, moves it to the Junk folder on the server) or drag it to another folder, the operation completes successfully, but the next message down in the message list is not selected, as it used to be. No message is now selected.
Comment 1 Milan Crha 2014-06-10 16:37:22 UTC
Thanks for a bug report. I cannot reproduce exactly this, but something similar. Let's have three messages in a folder:
   A
   B
   C

If I select message A and drag&drop it into another folder, then message B is properly selected, but when I drag&drop message C (the last in the list), then no message is selected.
Comment 2 Adam Williamson 2014-06-10 17:21:35 UTC
Welp, as I mentioned in my description:

"I sort my mail with the most recent first"

so that could account for the difference, if you have the ordering the other way around. Looks like it won't go 'back in time' to find another message to select.
Comment 3 Milan Crha 2014-06-11 06:39:54 UTC
Yeah, I tried with both sort orders, but I saw only what i described in comment #1, regardless of the sort type.
Comment 4 Milan Crha 2014-06-11 08:54:23 UTC
I caused this with my changes for bug #446659, or I just copied the issue in-together with my change. In any case, I tried to address this, hopefully in a proper way finally.

Created commit 1ec775d in evo master (3.13.3+) [1]
Created commit ca251c0 in evo evolution-3-12 (3.12.4+)

[1] https://git.gnome.org/browse/evolution/commit?id=1ec775d