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 260277 - collapsed thread view cannot get to next unread message
collapsed thread view cannot get to next unread message
Status: RESOLVED DUPLICATE of bug 216271
Product: evolution
Classification: Applications
Component: Do Not Use
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Product Design Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-06-16 13:02 UTC by Bryan W Clark
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bryan W Clark 2004-06-16 13:02:35 UTC
Description of Problem:
In a thread view you may collapse certain threads to save vertical space
and read other messages.  Once a thread is collapsed new message may arrive
inside the collapsed thread hierarchy.  Choosing 'Next Unread Message' does
not take you to the root message of a thread hierarchy, instead it does
nothing however Evolution still indicates that you have new messagees and
it's now your job to find them.

Steps to reproduce the problem:
1. Collapse a thread in the thread view with unread messages in the thread
2. Mark all other messages outside the collapsed thread as read
3. Use 'Next Unread Message' trying to find the unread messages in the thread

Actual Results:
The focus does not change

Expected Results:
The focus should move to the root message of the collapsed thread

How often does this happen? 
Every time
Comment 1 André Klapper 2004-12-08 00:37:45 UTC
damn still valid in evolution-2.0.2.0.200411260600-0.snap.ximian.10.1
and perhaps (?) related to bug 264987...although...don't know.
setting target milestone to 2.3.
this is not wishlist, but a bug, and could lead up to not realize 
important mail that should be answered...
Comment 2 André Klapper 2005-02-09 17:28:37 UTC
marking as a dup of bug 216271; targetting 16271 to 2.3.

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