GNOME Bugzilla – Bug 305831
Evolution-2.2.1.1 fails to properly restore vertical scroll postition of mail folders
Last modified: 2009-11-20 05:25:35 UTC
Version details: Evolution 2.2.1.1 Distribution/Version: Gentoo I have several mail folders. If I change to folder A, move the vertical scroll of the email list to some postition, change to folder B,then change back to A, the vertical scroll will be restored to where I left it, no matter if I moved it while in the other folder. If I start Evolution, got to folder A, move the vertical scroll of the email list to some position, close Evolution, then start it again - I will be in the folder where I was, the vertical scroll restored to where it was. Everything is OK so far. If I start Evolution, got to folder A, move the vertical scroll of the email list as far down as possible, close Evolution, then start it again - I will be in the same folder where I was but the vertical scroll will be at the top of the list, not at the bottom. It should be at the bottom, since I left it there. If after the startup I move to folder B, then back to A, the vertical scroll is restored to the end of the list, as it should be, so the problem occurs only on Evolution startup.
set the usability keyword.
Apologies for any spam... cc'ing usability-maint on all Evolution usability bugs. Filter on EVO-USABILITY-SPAM to ignore.
removing old 2.5 target milestone and retargetting to future - sorry.
Seems to work fine in 2.27.91 This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.26. Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.3 or 2.28.x or later), please reopen. thanks in advance.