[Tickets #2212] RESOLVED: Inconsistent folder refresh location

bugs@bugs.horde.org bugs at bugs.horde.org
Sun Jul 3 12:06:35 PDT 2005


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2212
-----------------------------------------------------------------------
 Ticket             | 2212
 Updated By         | kevin_myer at iu13.org
 Summary            | Inconsistent folder refresh location
 Queue              | IMP
 Version            | HEAD
 State              | Bogus
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-07-03 12:06) wrote:

All in all, kind of frustrating if you're trying to always have IMP jump to
the first unread message in a folder.  Take a non-hypothetical situation,
such as this:  1000 messages in a folder, sorted by any criteria.  Most of
the time, new messages will show up at either the end or the beginning of
the view, depending if you sort ascending or descending.  But you'll get a
fair number of stray messages dispersed throughout the index too.  If you go
and read one of those messages, and are ready to move onto the location of
the next unread message, how do you do that?  If the folder is the INBOX,
you can use the INBOX icon to get an updated message count and move to the
next unread message location.  If its not the INBOX, you have to expand your
folder structure and choose the folder, then click on it.  Or skip from
screenful of message to screenful of messages, and keep skipping until you
find the next unread message.  Whereas if the refresh was both a refresh and
a jumpto function, a quick Accesskey R would get you there - no folder
navigation and expansion necessary, no wasted time trying to find the next
unread message.  Software should provide functionality to process messages
more quickly, not force me to wade to find the next message to process.

I believe the behavior of a refresh should honor whatever value I choose for
mailbox_start, whether that refresh is automatic, forced, or implied, by
clicking on a folder.  Which really amounts to mailbox_start being expanded
to be "When opening or refreshing a mailbox, which page do you want to start
on?", which I think is a logical, useful extension.




More information about the bugs mailing list