91.1.3: Tray icon appears in the Windows tray when you start TB, with disabled "When Thunderbird is minimized, move it to the tray"
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: 8a03524c, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
- Uncheck the preference "When Thunderbird is minimized, move it to the tray".
- Restart Thunderbird.
Actual results:
The tray icon appears in the Windows taskbar tray as soon as Thunderbird starts, and stays there all the time whether TB is minimized or not, along with the main icon in the "running programs" area of the taskbar.
Expected results:
Preference checked + TB minimized -> icon in tray, no icon in "running programs" taskbar area.
Preference unchecked + TB minimized -> no icon in tray, icon in "running programs" taskbar area.
I just noticed that after reading the last unread message in my inbox, the tray icon at last disappeared, as per the corresponding preference setting.
Updated•3 years ago
|
I just noticed that after reading the last unread message in my inbox, the tray icon at last disappeared, as per the corresponding preference setting.
Tray icon reappears as soon as an unread message is in the inbox, despite disabled "When Thunderbird is minimized, move it to the tray".
Main taskbar icon remains.
Updated•3 years ago
|
Comment 3•3 years ago
|
||
It works as designed. Where there is unread mail, the icon appears.
It works as designed. Where there is unread mail, the icon appears.
It certainly does NOT. The tray icon appearance depends on whether or not the TB window is MINIMIZED, and that is ruled by a CHECKBOX in the PREFERENCES.
CHECKBOX ON = LITTLE ICON in the TRAY, NO BIG ICON in the TASKBAR MAIN AREA.
CHECKBOX OFF = the opposite.
What appears correctly is the BADGE with the unread mail count. That has nothing to do with this bug.
Comment 5•3 years ago
|
||
See also bug 1727874
Comment 6•2 years ago
|
||
Reporter, do you still see this issue when using version 102?
Resolved per whiteboard
Description
•