1969746 - Opening a pinned tab in a container results in the new tab also being pinned

Status: NEW

(Firefox :: Tabbed Browser, defect, P5)

Description

[Joel Kappes]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:139.0) Gecko/20100101 Firefox/139.0

Steps to reproduce:

Perform "Open in New Container Tab" on a pinned tab.

Actual results:

A new pinned container tab opens.

Expected results:

A new non-pinned container tab opens. If I wanted the tab to be pinned, I should have to perform one additional action to pin it once. If I didn't want the tab to be pinned I shouldn't have to perform an additional action to close it every time this happens.

Comment 1

[BugBot [:suhaib / :marco]]

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.

Comment 2

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Hello, thank you for the bug report!
Managed to reproduce this issue on:

• Firefox Nightly 141.0a1;
• Firefox 140.0b4(with Firefox Multi-Account Containers add-on enabled);
• Firefox 139.0.1(with Firefox Multi-Account Containers add-on enabled);

Tested on:

• Windows 10;
• macOS 15;

Setting as NEW so the developing team can have a look.

Comment 3

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit BugBot documentation.

Comment 4

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

I’ve ran mozregression but unfortunately I haven’t been able to pinpoint an accurate regression range. I have been able to reproduce the issue back to Firefox Nightly 73.0a1(2020-01-01), so I believe it’s safe to say that this isn’t a recent regression.

Comment 5

[Dão Gottwald [:dao]]

I think it's debatable whether this action should automatically pin the container tab. We should get input from UX on this before making any changes.