Open Bug 1930699 Opened 1 year ago Updated 10 months ago

Inconsistency as to whether each type of dialog window has its own icon

Categories

(Thunderbird :: OS Integration, defect)

Product:
Thunderbird
Component:
OS Integration
Version:
Thunderbird 115
Type:
defect

Tracking

(Not tracked)

Status:
UNCONFIRMED

People

(Reporter: psychonaut, Unassigned)

References

Details

As reported by a user at https://support.mozilla.org/en-US/questions/1470102 Thunderbird there is some inconsistency as to whether Thunderbird's various dialog windows (for showing event/task reminders, for composing messages, etc.) show a distinct icon in OS-level UI elements (the window title bar, the task bar, etc.) or show the generic Thunderbird icon. That user reports different behaviour across Thunderbird 115 and 128, but I am also seeing this issue and it doesn't seem to depend on the version of Thunderbird. Here's what I observe on my three machines:

  1. Machine running openSUSE Tumbleweed and Thunderbird 115: Separate icons for each kind of window.
  2. Machine running openSUSE Tumbleweed and Thunderbird 128: Separate icons for each kind of window.
  3. Machine running openSUSE Leap 15.5 and Thunderbird 115: Same icon for all windows.

It's not clear to me what the intended behaviour is supposed to be. (Though for as long as I can remember up until a few weeks ago, all my Thunderbird installations showed the same icon for all dialogs, and I prefer it that way.)

OK, so that at least establishes what the correct behaviour is. The problem is that some installations don't display the special icons, but rather use the default Thunderbird logo for all dialogs. Could be that this issue is a packaging problem; I've asked the OP on the support forum to indicate which OS they're using.

See Also: → 1931618

(In reply to Tristan Miller from comment #3)

Could be that this issue is a packaging problem; I've asked the OP on the support forum to indicate which OS they're using.

They never replied. SUMO shows it as X11; Linux x86_64; rv:131.0

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