Closed Bug 1963522 Opened 4 months ago Closed 3 months ago

List all tabs button's list messes up when opening/closing Tab Groups

Categories

(Firefox :: Tabbed Browser, defect)

Firefox 138
defect

Tracking

()

RESOLVED DUPLICATE of bug 1956254

People

(Reporter: bugzilla, Unassigned)

Details

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

Steps to reproduce:

In version 137, I had set browser.tabs.groups.enabled to true in order to check them out and it seemed to work ok.

In version 138, I opened one of the Tab Groups using the drop-down list from the List all Tabs button. I looked at the list of open tabs again and it doubled up everything. Here's what I saw: https://i.imgur.com/nA0cZQH.png

So I closed the tab group (save and close option) but the list all tabs drop-down was still showing some duplicated entries as well as listing all the Tab Group's item that were just closed. Screenshot: https://i.imgur.com/KWkxFOj.png

After opening and closing some other tab groups, It looked like this: https://i.imgur.com/JRESGjn.png

This also happened in a clean profile.

Actual results:

See what I did as I already talked about it.

Expected results:

Duplicate entries should not be shown and items removed when a tab group is closed.

Oh, the first two images were from my clean (well, cleaner) profile and the last image was from my normal profile after playing with it for awhile.

Component: Untriaged → Tabbed Browser

Looks like the latest 139 beta that I just tested corrects the issue.

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

For more information, please visit BugBot documentation.

Flags: needinfo?(sthompson)

Version 139 seems to have solved this issue.

I think this is a duplicate of bug 1956254 which was fixed in Firefox 139.

Status: UNCONFIRMED → RESOLVED
Closed: 3 months ago
Duplicate of bug: 1956254
Resolution: --- → DUPLICATE
QA Whiteboard: [qa-investig-done-c141/b140]
Flags: needinfo?(sthompson)
You need to log in before you can comment on or make changes to this bug.