Closed Bug 233098 Opened 21 years ago Closed 20 years ago

Taskbar title is the same as the message title

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 214896

People

(Reporter: andrew, Assigned: mscott)

References

Details

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

The taskbar title is the same name as the currently selected item in the
application.  This is confusing when you double click a message and it opens a
new window.  After you open the new window, the Thunderbird application and the
message window now have the same name in the task bar.  I would much rather see
the title of the thunderbird application just be "Thunderbird."  You could do
something like "Thunderbird: <Message_name>" to make it more descriptive if you
want, but don't allow it to be the same as the message name.  You could also
help by making the application Icon look like something other than an open
message for the main application (i.e. make it the thunderbird icon) and make
the message window look like the open message icon.  

Reproducible: Always
Steps to Reproduce:
1. Change your message window behavior in your prefs to "Open new messages in: A
new message window"  Also make sure you don't have taskbar grouping on (or just
make sure you know you have it on).
2. Double click an email message to open it in a new window
3. Notice the 2 applications in the task bar with the same name.  

Actual Results:  
Both applications in the taskbar have the same name and can not be distinguished.

Expected Results:  
The Thunderbird application should have the title "Thunderbird" and the message
window title be the message subject.
I note the same problem on Win ME.
*** Bug 240359 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 214896 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.