Using POP Mail, build 2000092908, 3 pane interface In my InBox I deleted several mails which were sorted by date. After each delete mail, Mail highlighted the next mail properly. Then I read a mail which I didn't delete and clicked the Next button. Mail didn't go the the Next mail in the sequence but jumped about 10 mails.
not a database problem - more likely a front end problem with the code that does navigation...
Assignee: bienvenu → putterman
Component: Mail Database → Mail Window Front End
did Next go to the Next Unread, or did it randomly jump 10 messages. The Next button does Next Unread not the next one in the list, in case that is what you thought it would do.
Not sure if it is the same bug, but "Next" or "N" does not work as it should in 2000100720. This is a simple situation that is difficult to explain in words so bear with me. 1. In a newsgroup with a long listing of messages in a sorted by thread, read some of the first messages at the top advancing through them by pushing "N" or the "Next" button. 2. Now manually scroll down to the bottom of the group and select a thread manually with the mouse. Read a child message of that thread and then push "N" or "Next". 3. Mozilla goes back up to the top and selects the next message after the last one you were reading at the top. EXPECTED: Mozilla should have advanced to the next unread message in the thread I was reading at the bottom. PS - If this is unrelated to this bug, please let me know so I can file it separately.
OK. After closing and re-opening Mozilla I can't get it to do this again, so just keep an eye out for it.
Cindy, have seen this behaviour in any of the latest nightlies?
I still see this behavior in 2001060409. It "jumped" about 30 mails forward when I clicked on "Next" after several "Deletes" in full pane.
User error. I thought this would go to the "Next" message not the "Next unread" message.
Mass removing self from CC list.
Now I feel sumb because I have to add back. Sorry for the spam.
reassigning to ssu.
Assignee: putterman → ssu
=>Invalid, per reporter's comment 7 ("user error").
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.