Open Bug 1738076 Opened 4 years ago Updated 4 years ago

New mail notification does not dispay as per Taskbar tray position

Categories

(Thunderbird :: Preferences, defect)

Thunderbird 91
defect

Tracking

(Not tracked)

People

(Reporter: anjeyelf, Unassigned)

Details

Windows 10 OS
Tested using TB 78.14.0 and TB Version 91.2.1

Position the computer TaskBar at bottom of screen
TB 78.14.0 = New mail notification pop up displays bottom of screen on right near 'Tray'.
TB 91.2.1 = New mail notification pop up displays bottom of screen on right near 'Tray'.
Result is correct for both versions.

Position the computer Taskbar at top of screen
TB 78.14.0 = New mail notification pop up displays top of screen on right near 'Tray'.
TB 91.2.1 = New mail notification pop up displays bottom of screen on right.
Result is correct for version TB 78.14.0
Failed result for version TB 91.2.1
It should auto display at the top of screen on the right side near the tray.

Position the computer TaskBar on left side of screen
TB 78.14.0 = New mail notification pop up displays on left side of screen bottom near 'Tray'.
TB 91.2.1 = New mail notification pop up displays bottom of screen on right.
Result is correct for version TB 78.14.0

Failed result for version TB 91.2.1
It should auto display on left side of screen bottom near 'Tray'.
The pop up said x account had a new message, but no content - no subject - a blank pop up. But I did notice this was a filtered email.

Position the computer TaskBar on right side of screen
TB 78.14.0 = New mail notification pop up displays on right side of screen bottom near 'Tray'.
TB 91.2.1 = New mail notification pop up displays bottom of screen on right. But, I think this is probably more due to similar default location than following tray location.

Basically:
version 78.14.0 will display the new mail notification near to the Taskbar Tray. no matter the position of the Taskbar. Top, Bottom, Left or Right of screen.

version 91.2.1 always displays in the same location; bottom right of screen. This is incorrect.
This is the bug.

You need to log in before you can comment on or make changes to this bug.