Firefox View in a non-private window should never show tabs from a private window
Categories
(Firefox :: Firefox View, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox115 | --- | unaffected |
firefox116 | --- | unaffected |
firefox117 | + | fixed |
People
(Reporter: bj, Assigned: sclements)
References
(Regression)
Details
(Keywords: nightly-community, regression, Whiteboard: [fidefe-firefox-view])
Attachments
(1 file)
Steps to reproduce:
- Create a new profile with Firefox View enabled and open several tabs and close some of them.
- Create a private window.
- Arrange the windows so Firefox View is visible in the non-private window and the private window has focus.
- Create a new tab in the private window and close it.
- Look at Firefox View.
Expected:
5) The recently closed tabs list should show the same view as after step 1.
Actual:
5) The closed tabs from the non-private window aren't displayed, and the closed tab from the private window is shown.
In other words, the private URL and private tab tile from the private window has leaked into non-private Firefox window.
If you start using tabs in the non-private window Firefox View will revert to showing tabs from that window. If you then go to the private window and create and close more tabs the closed tab list from the private window return to Firefox View.
Assignee | ||
Comment 1•1 year ago
•
|
||
I'm seeing this as well, but only in Firefox View, not any of the other history > recently closed tabs menus. It looks like we're not passing a window object in getClosedTabsData
here. Changing that in recently-closed-tabs to use getClosedTabsData(getWindow())
solves the issue but it seems like not getting closed tabs from private windows should be the default if no window object is passed in. I think this is an easy fix based on the work sfoster did in 1819675.
Comment 2•1 year ago
|
||
Set release status flags based on info from the regressing bug 1819675
Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
The bug is marked as tracked for firefox117 (nightly). However, the bug still has low severity.
:pluk, could you please increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 6•1 year ago
|
||
bugherder |
Assignee | ||
Updated•1 year ago
|
Description
•