Open Bug 520061 Opened 15 years ago Updated 2 years ago

Opening an email message in a new tab does not mark the message as read with "automatically mark as read" enabled

Categories

(Thunderbird :: Message Reader UI, defect)

Product:
Thunderbird
Component:
Message Reader UI
Type:
defect

Tracking

(thunderbird3.1 wontfix)

Status:
UNCONFIRMED
Tracking Flags:
Tracking Status
thunderbird3.1 --- wontfix

People

(Reporter: slyfoxlp, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 GTB5 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4 Opening an email message in a new tab should mark the message as read. This would be more convenient and would be consistent with the behavior of opening a email message in a new window. Reproducible: Always Steps to Reproduce: 1.double click a new email message or right click and select open in new tab 2.the email should be displayed in a new tab 3.when returning to the email list view the email should now be marked as read Actual Results: the email is not marked as read Expected Results: the email should be marked as read
Interesting idea. One could argue that it makes more sense to wait until the tab in question had actually been brought to the front before doing that marking, since it won't have been possible to actually read it until that time. It would be helpful to understand a bit more about the way in which you're reading messages and specifically the way in which you're using the "read/unread" flag here.
I read most email in view pane, but longer emails I will double click (which opens them in a new tab and gives it focus). After reading the email I either leave it open if I want to deal with it later or close if i'm done. I would prefer the message to be marked as read as soon as I open them (in either a new window or tab), but that is of course my user preference. So customizable option seems like the best choice to me, but UI consistency sounds like a must. Any other ideas, comments?
It does seem more consistent and would give an indicator in the message list of opened messages to users who are processing mail by opening it in tabs. Though I think this preference will vary a lot depending on the person.
I've seen this request also in hendrix. I'm concerned about making more complex than what we've already got via the "normal rules", i.e. mark per "automatically mark as read". If it isn't obeying existing rules, that's a bug IMO.
It does not mark a message as read by opening an unread message in a new tab and then closing the message tab. I feel that is inconsistent with the behavior that occurs when opening the same unread message in a new window (which appears to be immediately marked as read on message open). I feel the behavior should be made consistent by marking messages as read on opening a message into a new tab.
I don't see how anyone can argue that it should not be marked as read when opened in a new tab, when it is and always has been marked as read when opened in a new window. Surely this is just a way of sorting opened messages, either in windows or tabs. It should not change the behavior, should it? I would use the tabs, which I think are a great idea, but it's completely ruined for me by the loss of the escape key (to close it) and the message not being marked as read. It seems like a big oversight to me. What possible good reason can there be for that decision? I would of course be happy to be put right!
(In reply to comment #6) > I don't see how anyone can argue that it should not be marked as read when > opened in a new tab, slyfoxlp needs to clarify because we now have two different functionalities being argued - comment 2 and comment 5 seem to be asking for two different things. Comment 2 suggests the message should be marked read even if the message hasn't been read, and ignore "Automatically mark messages as read" setting (and other people have based their comments on that) - which would be an enhancement, i.e. new functionality. I would argue " This would be consistent with the behavior of opening a email message in a new window." is incorrect, because in that case, the message in the new window automatically has focus, and a message opened in a new tab does not. Conversely, comment 5 suggests the message isn't being marked read when the tab is switched to - which would be a bug. > I would use the tabs, which I think are a great idea, but it's completely > ruined for me by the loss of the escape key (to close it) Please file a bug for that if it doesn't already exist > and the message not > being marked as read. It seems like a big oversight to me. What possible good > reason can there be for that decision? I would of course be happy to be put > right! It's probably working OK for most people (as it is for me) or we'd be seeing a lot more complaints. When I say "works" I mean (if we add a step 0 to comment 0) 0. enable Options | Automatically mark messages as read that the message is marked read *after* I click on the message's tab giving the message focus (i.e. have read it), not before. If it isn't working that way for people then that's a bug. And a patch would be welcome.
Blocks: tabsmeta
I'm using 3.0.4 and when I have it set to open messages in a new tab, and I open a message, by double clicking or pressing enter, it *does* get focus. It never gets marked as read, when I close the tab, when I switch away from the tab, it stays unread at all times. So I don't understand why you think it doesn't get focus, and it *never* gets marked as read. > Please file a bug for that if it doesn't already exist It already exists. > If it isn't working that way for people then that's a bug. > And a patch would be welcome. Then it's a bug :) and I would do a patch but don't have the skills.
I'm confused. With option "automatically mark as read" on menu-->tools-->options... tab advanced-->reading&display, open a message in a tab mark message as read as happens when I open message in a new window (then the behavior is consistent). I can't reproduce this issue using STR in comment #0 provide by slyfoxlp and Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4pre) Gecko/20100408 Lightning/1.0b2pre Lanikai/3.1b2pre ID:20100408151251 Could be an issue only on the 3.0.x release? slyfoxlp what are your preferences on "reading&display" tab? Are you on imap server?
(In reply to comment #9) > slyfoxlp what are your preferences on "reading&display" tab? Are you on imap > server? slyfoxlp or Nigel also.
I tried it both ways, and have just done so again, and with "automatically mark as read" either on or off, and "open messages in" set to "new tab", messages never get marked as read (apart from if left for the time period specified when auto is on). As already stated, the tab always gets focus (when double clicking or opening with enter). I tried switching from tab back to inbox, and then back to the tab, and then closing the tab. With both the above setups (auto on or off). The message never gets marked as read. I am not on IMAP.
Ok. thanks for feedback. Also here today I'm on pop3 with this option: [x]automatically mark as read [x] immediately on display [ ] after displaying after x seconds Can you set also in the same environment for a test? Try the simplest thing: I now install your release TB 3.0.4 and you try to start TB in safe-mode to test if this is an extension related issue. See how to start TB in safe-mode here http://support.mozillamessaging.com/en-US/kb/Safe+Mode See you later for results.
I can't test this with "immediately on display" since it's marked as read before I get the chance to open it in a tab. I tried in safe mode, with "automatically mark as read" on and off, opening an unread message, switching back to inbox tab and then back to message tab, closing message tab. Always stays unread.
The confusion may be if slyfoxlp means in comment 0 item 2. that he's switched to the message tab - but that's not how it is written. (steps to reproduce are best if all actions are stated, eg. see ... do .... ) > So I don't understand why you think it doesn't get focus, and it *never* gets > marked as read. because a) comment 0 reads "1.double click a new email message or right click and select open in new tab" and b) (I'm in a fog and) I never use double click, so I was stuck on idea of "right click and select open in new tab", which does not give focus.
Severity: enhancement → normal
Summary: Opening an email message in a new tab should mark the message as read → Opening an email message in a new tab does not mark the message as read with "automatically mark as read" enabled
Mid-air collision with Wayne. I only add that this issue is raised only when preferences are as above [x]automatically mark as read [ ] immediately on display [X] after displaying after 5 seconds then execute STR as in comment #0 >1.double click a new email message or right click and select open in new tab >2.the email should be displayed in a new tab >3.when returning to the email list view the email should now be marked as read Confirmed Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4pre) Gecko/20100409 Lightning/1.0b2pre Lanikai/3.1b2pre ID:20100409033514
Status: UNCONFIRMED → NEW
Ever confirmed: true
> I never use double click, so I was stuck on idea of "right > click and select open in new tab", which does not give focus. I see, I agree it shouldn't be marked as read after right clicking and selecting "open in new tab". If it could be marked as read after switching to a tab opened in that way, that would be very nice! But it's the behavior after opening by double clicking or hitting enter that I'm after. Personally I would like to have a setting to automatically mark messages as read, only when they are opened. But that would be a new feature and beyond the scope of this bug report I guess. I've always lived with having to have them marked as read automatically after a time period, which I don't want, to get the functionality of having them marked read when I open them.
Set request for wanted-thunderbird3.1 for consistence with open message in new window
status-thunderbird3.1: --- → ?
Hey guys, the bug as I described (which I reported way back when in beta land) has been fixed. thanks, slyfoxlp
(In reply to comment #18) > Hey guys, > > the bug as I described (which I reported way back when in beta land) has been > fixed. > > thanks, > > slyfoxlp mumble... slyfoxlp do you have this options: [x]automatically mark as read [x] immediately on display [ ] after displaying after 5 seconds If yes I can't confirm that the bug is raised only when this options have the status described in comment #15. Another question: do you use imap?
I have the following checked: [x]automatically mark as read [ ] immediately on display [x] after displaying after 5 seconds having the tab open for 5 seconds marks it as read as expected. It might be nice to have an option to mark it as read immediately on open in new window/tab (but not when viewed in the preview pane). For that it should be 5 seconds. But that is a new feature request.
slyfoxlp do you use imap or pop3?
(In reply to comment #20) > It might be nice to have an option to mark it as read immediately on open in > new window/tab (but not when viewed in the preview pane). For that it should > be 5 seconds. But that is a new feature request. For a window, it's not a new feature, it's always been marked as read immediately on being opened in a window when "automatically mark as read" is on, and works that way now. The request is for tabs to work in the same way.
i'm using pop 3. immediately mark as read does not work in a way that I would like. I would want it to only mark a message as read when open in a new window (not viewed in the preview pane). But again, this would be a new feature.
I have the issue ONLY when I open the message in a new tab via double click on it. If I open the message via context menu, all work fine. slyfoxlp do you open message via context menu?
I typically open by double clicking a new message. However, I find the behavior to be identical via context menu and double click.
:-( it's my mistake, I'm fool: I have set "automatically mark as read" with "after displaying after" 55 seconds and not 5!.. I try in now setting "after displaying after" 1 seconds and all work as expected. Nigel and you? (In reply to comment #13) > I tried in safe mode, with "automatically mark as read" on and off For us is significant only when you have set "automatically mark as read" in other cases TB suppose that you want mark any message as read manually
Status: NEW → UNCONFIRMED
Ever confirmed: false
I've enabled automaticly mark as read immediately. If I open in new tab by double click it will open message in new tab by showing it to me and mark it as read. If I select via context menu open in new tab or just click third mouse button, it will open message in background tab and not mark message as read until I switched to tab, thus not until I've seen it.
(In reply to comment #27) > I've enabled automaticly mark as read immediately. If I open in new tab by > double click it will open message in new tab by showing it to me and mark it as > read. If I select via context menu open in new tab or just click third mouse > button, it will open message in background tab and not mark message as read > until I switched to tab, thus not until I've seen it. Yes but it will automatically mark it as read when viewed in preview pane. The issue is when it is set to mark after x seconds.
When I enabled "mark after 5 seconds" and open in new tab it works as suppose to be, marking it after 5 seconds as read for me. If you open tab in background it won't mark it as I described earlier.
(In reply to comment #29) > When I enabled "mark after 5 seconds" and open in new tab it works as suppose > to be, marking it after 5 seconds as read for me. If you open tab in background > it won't mark it as I described earlier. We have a misunderstanding. I have mine set to 60 seconds, because I don't really want that, unless I've been viewing it in the preview pane for a long time. With opening in a window, it marks emails as read *immediately* that they are opened OR after the time limit in the preview pane. The way I understand the time in seconds is that it has always applied to the preview pane, but if you open the email directly it gets marked immediately (since you obviously opened it to read it) whereas the time is because you could have something showing in the preview pane when you're not really reading it.
Thanks Nigel, yeah opening in new tab works correctly but if I open in new window will mark it immediately as read ignoring setting.
(In reply to comment #31) > Thanks Nigel, yeah opening in new tab works correctly but if I open in new > window will mark it immediately as read ignoring setting. I think opening in a new *window* works correctly! It's the tabs that are broken! The time limit has always been ignored when opening an email, and that's the way it should work I think. The time limit should only apply to the preview pane, since it indicates that you've read it if you've kept the email in the preview pane for that time. Why have a time limit when you open the email, you're obviously reading it. The time limit only makes sense when applied to the preview pane. That's the way it's always worked until tabs came along and it was logical.
(In reply to comment #32) > I think opening in a new *window* works correctly! It's the tabs that are > broken! For me its completely opposite. I'm running Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4pre) Gecko/20100408 Lanikai/3.1b2pre
(In reply to comment #33) > (In reply to comment #32) > > I think opening in a new *window* works correctly! It's the tabs that are > > broken! > For me its completely opposite. I'm running > Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4pre) Gecko/20100408 > Lanikai/3.1b2pre You said "if I open in new window will mark it immediately as read ignoring setting". It's the same for me. It's just I think that's correct and you think that's broken.
So you propose mark as read immediately message even when opening in new tab and ignoring settings about seconds, right?
(In reply to comment #35) > So you propose mark as read immediately message even when opening in new tab > and ignoring settings about seconds, right? Yes, that's right, to work in the same way as windows do and always have.
I know status 3.1 was requested a while ago, but we wouldn't change this on what is now a stable branch.
status-thunderbird3.1: ? → wontfix
See Also: → 502552

Wanting to switch to a cross-platform mail client (one for Windows and Linux).
While asking around for recommendations several colleagues mentioned the topic "when mails get marked as read" as a no-go for TB, but their experiences were years ago. Now I see this topic is still an issue.

Is there any tendency to work on it?

My Preferred Workflow

  • The read flag is used as a to-do-flag and works well with the web frontends of my mail providers. Also using it the same way at work with Outlook.
  • Message pane preview should not mark mails as read. Just taking a glance at the content to decide when to read, work and answer on it (immediately, later, a lot later, etc.)
  • Displaying a mail in a tab/window should mark it as read. Not immediately on open, as I may get distracted by something or have to react on something else, where I want close all tabs to start a new flow for it.
    • Note: Marking as read immediately on open is an acceptable compromise for me. Affected count of mails is low (<10) in my case.

Issues with TB 78.10.0 (Windows, 64-Bit) and My Workflow

No. 1:
With the following settings the preview message pane already marks the mail as marked :(

[x] automatically mark as read
   [x] immediately on display
   [ ] after displaying after [5] seconds

No. 2:
With the following settings when displaying the message in a tab/window then the mail is not marked as read :(

[ ] automatically mark as read
   [x] immediately on display
   [ ] after displaying after [5] seconds

The current options support only black and white, and do not provide flexibility for gray shades.

Preferred Solution

Considering all the comments I would suggest a multiple-choice setting for "Automatically mark messages as read":

  1. Always immediately (e.g. for folder option as described in https://bugzilla.mozilla.org/show_bug.cgi?id=411622 )
  2. When displayed in message pane preview (with optional delay)
  3. When opened in a tab/window, even if not displayed/focused e.g. via context menu Open in tab/window
  4. When displayed/focused in a tab/window (with optional delay)
  5. Never

Side notes:

  • Outlook has a separate setting if the message pane preview marks a mail as read or not, plus an optional delay.

Further optional settings/ideas:

  • Focus/Display first/top mail when mails opened in tabs/windows: ON/OFF
  • Message pane can mark mails as read: ON/OFF

Current Workarounds

  • Disable message pane preview and use mark automatically immediately, then try to decide on subject solely. If opened erroneously, then mark manually again as unread.
  • Use message pane preview and do not mark automatically at all, then manually mark as read when really read.

All unconvenient.

Severity: normal → S3

My testing of opening messages in tabs shows them being correctly marked as read.
Does the problem still reproduce for you?

Severity: S3 → S4
Flags: needinfo?(maddes+mozilla)

Status:
The message pane preview marking a mail as read still hinders my workflow.
For me the preview is just to have a glance at a mail, not to read and process it.
I still recommend a special setting for the message pane as written in #39.
The mentioned solution in #39 still stands as a feature request.

Retested with TB 102.4.1 (64-bit) on Windows 10 with latest updates.

No. 1a from #39
With the following settings the preview message pane still marks the mail as marked, although I just browsed through and haven't actually read it :(
A phone call can interrupt my browsing and the mail is previewed(!) for more than X seconds, so not a solution for me, also it applies to distinct display too.
For my workflow I would need different setting options as mentioned in #39.

[x] automatically mark as read
   [x] immediately on display
   [ ] after displaying after [5] seconds

No. 1b from #39
With the same settings opening a message in a new tab, then it is correctly only marked as read when the tab is actually displayed.
That was enhanced, and fits my workflow.

No. 2 from #39
That was just a test balloon, not retested.

Flags: needinfo?(maddes+mozilla)
You need to log in before you can comment on or make changes to this bug.