Open Bug 1808684 Opened 3 years ago Updated 2 years ago

On the macOS, pinned tabs cannot be saved after the window is closed

Categories

(Firefox :: Tabbed Browser, defect, P3)

Product:
Firefox
Component:
Tabbed Browser
Version:
Firefox 108
Platform:
Desktop
macOS
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr102 --- affected
firefox108 --- affected
firefox109 --- affected
firefox110 --- affected

People

(Reporter: linxin19812012, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: parity-chrome, parity-safari)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

  1. Open firefox on the macOS

  2. Open any page, such as https://www.mozilla.org

  3. Right click the tab to set the pinned tab

  4. Click the window close icon in the upper left corner to close the browser window

  5. Right click firefox on the taskbar to exit the browser

  6. Reopen the firefox browser

Actual results:

It is found that the previously set pinned tab is missing

Expected results:

The set pinned tab is reopened

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Tabbed Browser

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:108.0) Gecko/20100101 Firefox/108.0

Hi,

I am able to reproduce the issue in release 108, beta 109.0b8 and the latest nightly 110.0a1 (2023-01-06) on macOS 12. Also, I can reproduce it in 102.6.0esr.
The issue is not reproducible using Chrome.

Thanks for your input.

Severity: -- → S3
Status: UNCONFIRMED → NEW
Has STR: --- → yes
status-firefox108: --- → affected
status-firefox109: --- → affected
status-firefox110: --- → affected
status-firefox-esr102: --- → affected
Ever confirmed: true
OS: Unspecified → macOS
Hardware: Unspecified → Desktop

Any progress on this?

Flags: needinfo?(dao+bmo)

This is basically a mac-specific variation of bug 587400.

Blocks: pinnedtabs
Depends on: 587400
Flags: needinfo?(dao+bmo)
Priority: -- → P3

When did the expected behaviour of closing a window with pinned tabs change?
This looks like parity-safari, no other browser works this way, afaics.

(In reply to matthias koplenig [:metasieben] from comment #7)

When did the expected behaviour of closing a window with pinned tabs change?

Are you saying this used to work as you'd expect? If so a regression range would be helpful.

Flags: needinfo?(mozilla)
Keywords: parity-chrome, parity-safari, regressionwindow-wanted

Sorry, :dao, I should have been more precise.

The behaviour outlined in comment 0 has never been in Fx, since closing a window closes ALL the
tabs contained in that window. This has been the case ever since app tabs were introduced.

In my (limited) testing only Safari behaves this way, although their way of handling pinned tabs
is quite different from our way(eg in Safari the URL of a pinned tabs is "fixed", getting reset
when restarting browser).

Maybe this bug should simply be duped to bug 587400, since in the end it's exactly the same, some users
expect app-tabs to be permanent, others don't.

Flags: needinfo?(mozilla)

Maybe this is too semantic an argument, but what is the meaning of "pinned" if they are so fleeting? This feature is next to useless as it is. My solution:
Reproduce the same pinned tabs in every window opened. Problem solved. The number of users who are expecting a different set of pinned tabs for each window has to be next to zero.

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