Open Bug 1321406 Opened 8 years ago Updated 1 year ago

Restarting with "Restore previous session" and only pinned tabs gives an unwanted Homepage tab

Categories

(Firefox :: Session Restore, defect)

Product:
Firefox
Component:
Session Restore
Type:
defect

Tracking

()

People

(Reporter: asa, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dupeme) 

If I have one tab open and restart the browser I get that one tab back. If, on the other hand, I have one pinned tab open and restart the browser I get that pinned tab AND a new tab I didn't ask for. 

Steps to reproduce:
1. pin a single tab
2. ensure no other "regular" (non pinned) tabs are open
3. closer and reopen the browser

Results: one pinned tab and one new tab
Expected: just the one pinned tab
Component: Tabbed Browser → Session Restore
Whiteboard: [DUPEME]
Keywords: dupeme
Whiteboard: [DUPEME]

This is related to bug 422189. This is a situation where my "show my windows and tabs from last time" is not being honored--an extra tab is being added to my tabs from last time.

If there are pinned tabs, but nothing else to restore, show only pinned tabs.
It should be at least possible to configure this behavior.

Updated the title to reflect that the unwanted created tab is the page specified in the "Homepage and new windows" setting on about:preferences#home.

Summary: restarting with only pinned tabs gives an unwanted new tab → Restarting with "Restore previous session" and only pinned tabs gives an unwanted Homepage tab
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates and 22 votes.
:dao, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Flags: needinfo?(dao+bmo)

(In reply to Release mgmt bot (nomail) [:suhaib / :marco/ :calixte] from comment #8)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

It is still relevant. I run Nightly on two systems so I am typically annoyed by this bug four times a day.

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