Closed Bug 552921 Opened 14 years ago Closed 14 years ago

Remember last active tab and return to last active tab on closing tab

Categories

(Thunderbird :: Mail Window Front End, enhancement)

x86_64
Windows Vista
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 508776

People

(Reporter: blintjens, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Win64; x64; Trident/4.0; GTB6.4; .NET CLR 2.0.50727; SLCC1; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3

When having multiple tabs open, it would be nice that the last active tab re-activated on closing another tab.

For example, having the mail tab (let's call this Tab1) and the calendar (lets call this Tab2) open, on opening a mail message from TAB1, will open a new tab with the message (TAB3). Now, closing the message (Tab3), the calendar tab (tab 2) will be activated. 

In this case it would be nice the mailtab (tab1) would re-activate as the closed tab origionated from this tab.

Reproducible: Always

Steps to Reproduce:
Start Thunderbird
1.Open calendar (or any other) as a second tab
2.Activate the E-mail tab (first tab) and open a message (again as a new tab)
3. Close this opened message.

Actual Results:  
The previouse tab will be activated on closing a tab (being the calendar in our example.)

Expected Results:  
The tab from which the closed tab originated (the parent?) should activate (being the e-mail tab in our example)

If not already, tabs should prehaps have a parent/child relation like other windows. Once this has been implemented, this request should almost become default behaviour or at lease quite easy to implement.
Summary: Remember alst active tab and return to last active tab on closing tab → Remember last active tab and return to last active tab on closing tab
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.