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 232314 - next new message on newly opened folder doesn't scroll message list
next new message on newly opened folder doesn't scroll message list
Status: RESOLVED DUPLICATE of bug 231413
Product: GAL
Classification: Deprecated
Component: ETable
trunk
Other other
: Normal trivial
: ---
Assigned To: Radek Doulik
Evolution QA team
: 231426 234417 234698 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-10-15 17:16 UTC by Ian Peters
Modified: 2005-08-24 11:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ian Peters 2002-10-15 17:16:00 UTC
Normally, when you press the ']' key after selecting a folder, you are
taken to the next unread message, and the message list scrolls to display
this message as well.  However, if the folder has just been opened for the
first time, the message display shows the first unread message, but the
message list doesn't scroll to the newly hilighted message, which is a pain.
Comment 1 Jeffrey Stedfast 2002-10-15 20:44:15 UTC
this actually only happens if you click '.' or ']' fast enough (before
etable finishes rendering maybe? I dunno)

anyways, this is actually an etable bug afaict since the mailer just
tells etable to select the message and etable is supposed to handle
all the scrolling.
Comment 2 Ian Peters 2002-10-15 21:04:45 UTC
This happens for me no matter how long I wait before pressing '.' or
']' in a new folder, so it doesn't appear to be a race condition for me.

I did mention this to clahey, who also seems to think it's an etable
bug, and might have some ideas on how to fix it.
Comment 3 Gerardo Marin 2002-11-27 19:47:01 UTC
*** bug 234698 has been marked as a duplicate of this bug. ***
Comment 4 Gerardo Marin 2002-11-27 19:47:29 UTC
*** bug 231426 has been marked as a duplicate of this bug. ***
Comment 5 Gerardo Marin 2002-12-09 20:45:11 UTC
*** bug 234417 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2005-08-24 11:09:33 UTC

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