The "Move Tab to New Window" option should not be available if there's only one tab
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox-esr140 | --- | wontfix |
| firefox139 | --- | unaffected |
| firefox140 | --- | wontfix |
| firefox141 | --- | wontfix |
| firefox142 | --- | wontfix |
| firefox147 | --- | wontfix |
| firefox148 | --- | wontfix |
| firefox149 | --- | verified |
People
(Reporter: acristea, Assigned: aaryamannsingh3)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: good-first-bug, regression, Whiteboard: [fidefe-tabgrps])
Attachments
(2 files)
Found in
- Nightly 140.0a1
Affected versions
- Firefox 139.0
- Nightly 140.0a1
Tested platforms
- Affected platforms: macOS 13 ARM
Steps to reproduce
- Go to about:preferences#general
- Enable "Vertical tabs" from Browser Layout
- Have only one tab open in Sidebar
- Right-click on the tab
- Select "Move Tab" > "Move to New Window"
Expected result
- The "Move Tab" > "Move to New Window" option is disabled.
Actual result
- The "Move Tab" > "Move to New Window" option is not disabled.
Regression range
- Not sure if this is a regression. If there is one I will find it asap.
Updated•10 months ago
|
Updated•10 months ago
|
Updated•10 months ago
|
Updated•10 months ago
|
Comment 2•10 months ago
|
||
I investigated for regression range by running mozregression between 2025.05.13 and 2025.05.25, found the folllowing:
Last good revision: 50168e035edfe105d0a574e63947e8d0b35a0be9
First bad revision: e6cd6f4fb15b654b22c328f500d1699e8c04d28a
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=50168e035edfe105d0a574e63947e8d0b35a0be9&tochange=e6cd6f4fb15b654b22c328f500d1699e8c04d28a
point to bug 1921835
Investigated on macOS 10.15, not reproduced on 138.0.4, 139.0 and 139.0b10.
Updated•10 months ago
|
Comment 3•10 months ago
|
||
Comment 0 mentions 139.0 is affected, but the regressor versions in Comment 2 indicate that only Fx140+ is affected.
Comment 4•10 months ago
|
||
:jswinarton, since you are the author of the regressor, bug 1921835, could you take a look?
For more information, please visit BugBot documentation.
Updated•10 months ago
|
Comment 5•10 months ago
|
||
Next week is the final week of beta for Fx140
:jswinarton, do you plan on having a patch in time and requesting a beta uplift?
Comment 6•10 months ago
|
||
Hi :dmeehan, I have plans to investigate this but I am not sure I will have time before the beta uplift. I think it would be better to target this for 141.
Updated•10 months ago
|
Updated•10 months ago
|
Updated•9 months ago
|
Comment 8•9 months ago
|
||
Hi Pascal, we have not had time to investigate this as part of this cycle. I am not sure we will have time until at least 143. I will raise this with our team in our next planning session.
Updated•9 months ago
|
Updated•8 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Comment 9•5 months ago
|
||
Looks like it was indeed regressed by bug 1921835.
Code was patched to:
let visibleOrCollapsedTabs = gBrowser.tabs.filter(
t => t.isOpen && !t.hidden
);
let allTabsSelected = visibleOrCollapsedTabs.every(t => t.multiselected);
contextMoveTabOptions.disabled = this.contextTab.hidden || allTabsSelected;
This used to call gBrowser.allTabsSelected() which has an explicit check for this.visibleTabs.length == 1.
Any fix for the "disable the menu option with one lone ungrouped tab in a window" case should also account for collapsed tab groups. If the tab strip has 1 collapsed tab group and 1 ungrouped tab, the ungrouped tab should still be allowed to move into a new window even though it is the only visible tab in this case.
Updated•5 months ago
|
Updated•5 months ago
|
Comment 10•3 months ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 11•2 months ago
|
||
(In reply to Stephen Thompson [:sthompson] from comment #9)
Looks like it was indeed regressed by bug 1921835.
Code was patched to:
let visibleOrCollapsedTabs = gBrowser.tabs.filter( t => t.isOpen && !t.hidden ); let allTabsSelected = visibleOrCollapsedTabs.every(t => t.multiselected); contextMoveTabOptions.disabled = this.contextTab.hidden || allTabsSelected;This used to call
gBrowser.allTabsSelected()which has an explicit check forthis.visibleTabs.length == 1.Any fix for the "disable the menu option with one lone ungrouped tab in a window" case should also account for collapsed tab groups. If the tab strip has 1 collapsed tab group and 1 ungrouped tab, the ungrouped tab should still be allowed to move into a new window even though it is the only visible tab in this case.
Looking into this bug
| Assignee | ||
Comment 12•2 months ago
|
||
Updated•2 months ago
|
Comment 13•2 months ago
|
||
Comment 14•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Comment 15•2 months ago
|
||
Verified as fixed with nightly Firefox 149.0a1 (2026.02.05) on macOS 10.15, now The "Move Tab" > "Move to New Window" option is disabled, having only one tab opened in vertical sidebar.
Description
•