STR: 1. Have the following folder structure and statuses A ├ B (unread, no new messages, appearing black and bold) ├ C (no unread, no new, appearing black and regular) └ D (unread and new, appearing blue and bold) 2. Click on D 3. Collapse A but *without* selecting A itself EXPECTED: A should appear black and bold because after clicking on D there are unread (and no new) messages in A's subfolders. ACTUAL: A appears bold and blue (just like before clicking D). To make A appear as it should D must be unselected first (by selecting another folder). version 3.17.3git143
The "new" flag from new messages is removed only after you leave the folder, not when you enter it. And since by collapsing the parent folder, you merely hide the active folder from view, but not leave it, there is no reason why the collapsed parent folder shouldn't be blue - it does have a child folder with new messages.
> The "new" flag from new messages is removed only after you leave the folder, not when you enter it. I know that. That's the reason for the bug report. It seems wrong logic. > there is no reason why the collapsed parent folder shouldn't be blue - it does have a child folder with new messages But once the folder is selected they are no longer new. They are just unread. Why should the be more "new" while one is in the folder and less "new" when one leaves the folder? If the purpose of having separate "new" and "unread" states is to indicate that a particular folder contains messages which one has neither read, nor even seen in the list - as soon as the folder get selected this purpose is served and there is no need to sustain the "new" state. Or is there a different purpose of the "new" state?
(In reply to comment #2) > > The "new" flag from new messages is removed only after you leave the folder, not when you enter it. > > I know that. That's the reason for the bug report. It seems wrong logic. > [...] > Or is there a different purpose of the "new" state? Yes, the purpose is to be able to actually see which are the new messages. The logic is not wrong, just different from what you seem to have expected. Also, if you want to report a bug about thing X being wrong, do not open a bug report about some secondary effect caused by thing X. It does not help anyone, and only creates confusion.
Sorry about the confusion. I just thought that the logic is wrong and that that may be a bug. > Yes, the purpose is to be able to actually see which are the new messages. This seems even more confusing as there is no way to distinguis new messages from unread ones. That is exactly the reason for why I thought the logic might be wrong: Once the folder is clicked there is no visual cue which messages are new. So as they are all the same (unread) it would make sense the folder state to reflect that (unread) instead of a state which corresponds to nothing observable (new).