after check message sorting is not correct

[spriebe]

After check_recent the sorting is not correct anymore. perhaps we should initiate a javascript sorting click or so?

[thomasb]

New messages are added at top of the list. I think this is OK because the users don't want to search for the new messages when they arrive. Other opinions?

[seansan]

Set to later until we have more input on discussion

[houchin]

The problem with the current behavior is that messages are sorted older to newer, the message list will likey be scrolled to the bottom, thus new messages are added off screen and the user will have to hunt for them.

If sort by date is currently selected, I believe it would be OK for the messages to be added to the end (sort by receive date, not by send time [although those times should be very, very close together]).

However, if messages are sorted by another field, RC should respect that sorting.

[thomasb]

And what if the new message would be placed on another page than the one which is currently displayed? Then we can only update the unread count and the user needs to "seek" for the new message. If sorted by subject, how should the user know what the subject of the new message is and on which page it can probably be found? That doesn't make sense to me.

[alec]

For me it does make sense, but we must implement filtering by /Seen flag.

[houchin]

If the new messages add a page to the message list, then you move to the page with the first new message if the user had already been at the "most recent" page. This appears to be what gmail goes, although I could only see how to put messages in one direction.

I set it to put 25 messages per page, then sent myself 40 new messages. As the messages arrived, it put the new ones in the list and moved me to the most recent page.

This is about doing what the user specified through the preferences/settings you've already implemented.

* If messages are sorted older to newer

• put new messages at the end of the list
• If the user had already been at the last page and the old number of messages was a multiple of the page size, go the next page
• If the user had already been at the last page but the first new message would still be displayed on this page, stay put

* If the messages are sorted newer to older

• put new messages at the beginning of the list
• Stay at the first page

This is also mimicing what desktop mail clients do. When I'm scrolled to the middle of a message list in my desktop client and I get a new message, it doesn't just plop the message anywhere in the list, and it doesn't scroll me to that new message. It respects my current settings and puts the message where it belongs. -