This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Some messages don't get marked "read" for a long time after opening

  • 4 respuestas
  • 0 tienen este problema
  • 66 visitas
  • Última respuesta de Matt

Mikey
Mikey
more options

Hi. I'm using T-bird v 115.3.2, and since the upgrade to 115, I've been seeing weird behavior regarding opening messages vs their getting marked read.

I'm referring to actually opening the message in a new window (I do not use the preview window--it is turned off).

My usual reading behavior is to open a message, read it, then press <F> to go to the next message. In either case, most messages immediately get marked as read. However, some random messages do not get marked as read immediately--after a delay, the message gets marked as read. It seems to be related to messages from some specific senders, as opposed to random messages. For example, marketing messages from Southwest Airlines always seem to have this issue, as do the daily newsletters from "The Hustle."

What are the criteria for T-bird to think a message has been read? If it matters, I'm seeing this on mailboxes where I use IMAP access. I have not seen it occur in the mailbox where I use POP3 access, but almost all of those messages are plain text.

Hi. I'm using T-bird v 115.3.2, and since the upgrade to 115, I've been seeing weird behavior regarding opening messages vs their getting marked read. I'm referring to actually opening the message in a new window (I do not use the preview window--it is turned off). My usual reading behavior is to open a message, read it, then press <F> to go to the next message. In either case, most messages immediately get marked as read. However, some random messages do not get marked as read immediately--after a delay, the message gets marked as read. It seems to be related to messages from some specific senders, as opposed to random messages. For example, marketing messages from Southwest Airlines always seem to have this issue, as do the daily newsletters from "The Hustle." What are the criteria for T-bird to think a message has been read? If it matters, I'm seeing this on mailboxes where I use IMAP access. I have not seen it occur in the mailbox where I use POP3 access, but almost all of those messages are plain text.

Todas las respuestas (4)

Mikey
Mikey Autor de la pregunta
more options

An update to this issue: T-bird updated itself and now is version 115.5.1. However, the issue persists.

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

There are a number of open bugs which might be a match; https://bugzilla.mozilla.org/show_bug.cgi?id=814665 https://bugzilla.mozilla.org/show_bug.cgi?id=1673380 https://bugzilla.mozilla.org/show_bug.cgi?id=537600 https://bugzilla.mozilla.org/show_bug.cgi?id=1226125

I could see any of those being related or exactly matching. It is not an exhaustive list, I just don't have time to work through them all.

Mikey
Mikey Autor de la pregunta
more options

Thank you for the references. This is the first time I've posted about an issue... normally, I can find the answer through web searching. I'll do some research through the bug reports.

Those bug reports reference older versions, and this issue started for me with 115. The issue may be related, though.

Thanks!

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

The key factor is of the bug is "Open" not the version it was first observed in.

Fundamentally there are issues, I think that perhaps the move to defaulting to threaded views of mail may have in some way made a preexisting bug more obvious, rather than there being a new bug. I say this based more on the lack of change in the code for marking a message as read than any real knowledge.

It may also have something to do with those using the card view of mail instead of the traditional list view, as it uses a completely new display "component".

Please post a link to any bug you may file, or any result you get. There have been a number of posts about messages marking as read, and they appear to mostly revolve around the view in a window view. But any concrete information with steps to reproduce will see a bug that is actionable, rather than a report of an anomaly.

Modificadas por Matt el