Closed Bug 1545920 Opened 5 years ago Closed 5 years ago

No need to open new tab if browser starts with pinned tabs

Categories

(Firefox :: Session Restore, defect)

68 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1321406

People

(Reporter: bugzilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

I have 3 pinned tabs and sometimes I have no unpinned tabs open.

Actual results:

When FF is started with a setting to restore last tabs state it shows 3 pinned tabs AND it opens one new tab.

Expected results:

If the browser has some pinned tabs on startup it should not open additional new tabs.

Hi @Revertron, tested this issue on:
[Windows 10]
[Firefox versions]: latest nightly 68.0a1, release 66.0.3 and release 60.0
=> here is the behaviors= * restore session should be checked - on all versions when tabs are pinned a new tab is open along with those pinned tabs. When simple tabs are opened after restarting the browser no new tab will be opened. For me it seems that to be an intended behavior with the pinned tabs.
Additionally, I have a question: Sometime in the past you encountered this behavior (new tab opened having pinned tabs)? If you don't this could be reported as an enhancement rather than a bug. I will set a component to it and maybe someone from dev's team could help us with that.
Thanks for your contribution.

Component: Untriaged → Session Restore

No, I don't think it is a bug, it is truly an enhancement.
One more thing: if I close FF with one of the pinned tabs selected and have some simple tabs, it is selected upon the restart, but if I don't have simple tabs, then the newly created simple tab steals the focus :(

Right, but as I said above is the same result no matter which pinned tab you focused, as long as pinned tabs are involved the result is the same.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.