When I have a mail in three Labels, and I read it in one, it is often marked as read in one of the other two folders while unread in the last one. If I read (say) 10 unread mails in my Inbox, reading the first 7 for a long time and quickly glancing over the last three, just to make them read, and immediately go to All Mail, TB checks for new mails and marks ONLY the last three as read, leaving the first seven that I took a long time to read as unread. By this logic, the reverse issue should affect us in theory, and it does.Ģ. If the initial problem is understood, this should be as well, because one of the reasons (I'm coming to the other) this problem exists is that TB doesn't recognize the Label system, and tries to apply the folder system to GMail. I can read the mail in All Mail and then check the mail in the other 'Labels' that mails is in and the mail will not be marked as read in these other Folders/Labels. But read on, I think this issue can be fixed in a different way)ġ. (Unless you want TB to check the message ID, which may or may not be a nice thing to do. This is expected behavior and this is not where we want to fix this bug. Put simply, TB is coded to believe that only it is capable of marking a mail read or unread while it is running.
(Yes, zero) It seems to me that TB doesn't expect mails to be marked as unread on the server when it hasn't done marked it itself. I'm really not sure which bug I'm talking about (i.e Bug 502370 or Bug 518581), but I have noticed a few things here:Ġ.
0 kommentar(er)
