Move tab to Start/ End options are enabled and not working, even if the Split View tab is already at start/en,d and the other view is focused
Categories
(Firefox :: Tabbed Browser: Split View, defect, P3)
Tracking
()
People
(Reporter: atrif, Assigned: nobleugwuja)
References
(Blocks 1 open bug)
Details
(Keywords: good-next-bug, Whiteboard: [fidefe-splitview][outreachy-sidebar-2026])
Attachments
(2 files, 2 obsolete files)
Found in
- 149.0b1
Affected versions
- 150.0a1 (2025-02-24)
- 149.0b1
Tested platforms
- Affected platforms: macOS 26, Ubuntu 24, Windows 11
- Unaffected platforms: none
Steps to reproduce
- Move a Split View to end on the tab bar.
- R-Click on the left view and select the Move tab option.
Expected result
- The move tab to End is greyed out.
Actual result
- The move tab to end is available and does nothing
Regression range
- not a regression.
Additional notes
- Attached a screen recording.
| Reporter | ||
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 3•1 month ago
|
||
I've reproduced this on my local build. On my build the option appears greyed out but still shows a hover effect and is not fully disabled. I'm ready to start investigating the fix.
Updated•1 month ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
| Assignee | ||
Comment 5•1 month ago
|
||
Patch is up for review: https://phabricator.services.mozilla.com/D290115.
This fix makes sure the 'Move' options in the context menu respect the boundaries of the entire Split View tab. This stops the 'Move to Start/End' from staying active when the split is already at the edge. Tested with pinned tabs too!
| Assignee | ||
Comment 6•1 month ago
|
||
| Assignee | ||
Comment 7•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 9•1 month ago
|
||
| bugherder | ||
Comment 10•1 month ago
|
||
The patch landed in nightly and beta is affected.
:nobleugwuja, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox150towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 11•1 month ago
|
||
(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #10)
The patch landed in nightly and beta is affected.
:nobleugwuja, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox150towontfix.For more information, please visit BugBot documentation.
I'm not sure if this requires an uplift. But I'd appreciate guidance on the right call here.
Comment 12•1 month ago
|
||
Checking with :sclements on if we want to uplift this to beta or not
Updated•1 month ago
|
Comment 13•1 month ago
|
||
We're not going to uplift this since its a minor issue with low severity.
Updated•1 month ago
|
Updated•18 days ago
|
Description
•