TB78 Clicking an unread message marks it read after 4 seconds
Categories
(Thunderbird :: Message Reader UI, defect)
Tracking
(Not tracked)
People
(Reporter: mb75048, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
- In Preferences -> General -> Reading & Display: check "Automatically mark messages as read" and check "After displaying for 4 seconds".
- In the message pane, click on an unread message and then click away to a different message.
Actual results:
After 4 seconds, the clicked/unclicked message was marked as read.
Expected results:
In TB 68.x, the message remained unread. The purpose of the setting "After displaying for N seconds" used to be to avoid marking a clicked message as read if one clicked away from it before the N seconds but in TB 78.0.1, the purpose appears to have changed for the worse IMO.
|
||
Comment 1•5 years ago
|
||
Hmm, I cannot reproduce this. For me it is marked read at 5 seconds.
(In reply to Wayne Mery (:wsmwk) from comment #1)
Hmm, I cannot reproduce this. For me it is marked read at 5 seconds.
Are you clicking on the unread message and then clicking away, pls? In TB 68.x, this prevented the message from being marked as read while in 78.0.1, it causes the message to be marked as read after N seconds even after I clicked away from it.
|
|
||
Comment 3•5 years ago
|
||
Yes. I'm also on a Mac. But using beta Thunderbird, so slightly newer than 78.0.1. You might try 78.1.0 just out, but I doubt it will make a difference.
(In reply to Wayne Mery (:wsmwk) from comment #3)
Yes. I'm also on a Mac. But using beta Thunderbird, so slightly newer than 78.0.1. You might try 78.1.0 just out, but I doubt it will make a difference.
Unfortunately 78.1.0 behaves the same afaict. But it looks like the beta version addresses it perhaps so I will wait for the next release. Thank you very much for taking a look.
|
||
Comment 5•5 years ago
|
||
@ mb75048:
I can't reproduce your issue.
If I check "After displaying for 5 seconds", then click on a message in the thread pane, it is opened in the message pane and will be marked as "read" after exactly 5 seconds.
If I click on another message in the thread pane* before* 5 seconds it will be opened immediately and the first message will stay marked as unread.
Actually I observe the same behavior in both TB 68.x.x and TB 78.1.0-candidates/build2
@Eckard Berberich - I wonder if the View is relevant? In my case, View->Layout is set to Vertical View + Folder Pane + Message Pane. I definitely see the behavior on TB 78.1.0 now as well in the Unified Inbox as well as the any of the individual inboxes. My value is also 4 seconds vs. 5 - I set it to the latter and the behavior didn't change. Is there anything else that I can check pls?
|
|
||
Comment 7•5 years ago
|
||
I tested your issue both, in "classical view" and in "vertical view", and still cannot reproduce it.
Does this issue also appear in a new, pristine profile ?
@Eckard Berberich - I launched TB with a new profile and can confirm that the issue does not happen with it. For now, I will work around it by disabling the 'Automatically mark messages as read' feature until I can recreate my proper profile.
|
||
Comment 9•5 years ago
•
|
||
wfm on Win10, 78.1.0 (64-bit). I often use "M" key to mark read and on gmail IMAP account, and I sometimes observed that it keeps toggling read/unread unexpectedly when pressing the key. But I've never seen behaviour reported here.
|
|
||
Comment 10•5 years ago
|
||
If you use the original profile, anything stand out in tools > developer > error console during startup or attempting to mark message as read?
|
Reporter | |
Comment 11•5 years ago
|
||
@wsmwk unfortunately no relevant errors showed up in the error console when I re-enabled the setting (automatically mark as read, 4 seconds), clicked on an unread message, and then clicked away within a second. Here is what was generated in the console:
(warning) Request to access cookie or storage on “<URL>” was blocked because we are blocking all third-party storage access requests and content blocking is enabled. 15
(error) 2147942487
The above numerical error was strange - there was no locating or other information attached to it.
|
||
Updated•5 years ago
|
Description
•