Closed Bug 144208 Opened 22 years ago Closed 22 years ago

[RFE] After closing a tab, focus should shift to the tab from which closed tab was originally spawned

Categories

(SeaMonkey :: General, enhancement)

Product:
SeaMonkey
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 105722

People

(Reporter: mrmazda, Assigned: mpt)

Details

Currently, when a tab is closed, focus shifts to the tab to the left of the
position occupied by the closed tab. I've been unable to find a compelling logic
for such behavior.

The behavior in the summary is one I would find vastly superior to the current
or alternative other behaviors. Some places that explain why this would be
preferable can be found in such places as bug 105722, bug 115234, bug 131037,
bug 144154 and multiple newsgroup threads, so I see no compelling reason to
duplicate it here.

Cf. bug 144207.
Summary: After closing a tab, focus focus should shift to tthe tab from which closed tab was originally spawned → [RFE] After closing a tab, focus should shift to tthe tab from which closed tab was originally spawned
I fully agree that this proposed behaviour is far superior to the current
nonsensical one.

If selecting which behaviour via preference is denied us (bug 131037), then
let's at *least* make sure the *only* option makes sense.
Summary: [RFE] After closing a tab, focus should shift to tthe tab from which closed tab was originally spawned → [RFE] After closing a tab, focus should shift to the tab from which closed tab was originally spawned
And what should happen if the "tab from which closed tab was originally spawned"
has already been closed ?
Focus the left tab ? The right ? The newest ? The oldest ? Random ? New Pref ?
TBD. I suggest most recently accessed.

*** This bug has been marked as a duplicate of 105722 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.