Closed
Bug 1907058
Opened 3 months ago
Closed 2 months ago
Refactor gBrowser.moveTabTo logic to account for new pinned tabs container
Categories
(Firefox :: Sidebar, task)
Firefox
Sidebar
Tracking
()
RESOLVED
MOVED
People
(Reporter: sclements, Assigned: sclements)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-sidebar])
In bug 1899336, pinned tabs are moved into a new container so as to style them in a grid format and to allow for scrolling. But all of the existing logic in tabbrowser.js and tabs.js assumes that pinned tabs are always in the arrowscrollbox but positioned at the front. Some aspects have been reworked in bug 1899336, but not the different "Move To.." menu options in the right-click tab menu. Refactoring that looks to be a bit more involved so I'm breaking this off separately.
Updated•3 months ago
|
Assignee | ||
Updated•3 months ago
|
Summary: Refactor MoveTo logic to account for new pinned tabs container → Refactor gBrowser.moveTabTo logic to account for new pinned tabs container
Assignee | ||
Updated•3 months ago
|
Assignee: nobody → sclements
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•2 months ago
|
||
Addressing this in bug 1899336.
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → MOVED
You need to log in
before you can comment on or make changes to this bug.
Description
•