Distribution
Mint 22.3
Package version
6.6.3
Frequency
Always
Bug description
I belive this is not "by design" - it's a usability regression. The normal behaviour is l support bidirectional tab movement. Nemo's half-implementation trains false expectations then punishes users.
Detached tabs/windows are "one-way" - no reattach/move.
Steps to reproduce
Open Nemo and create multiple tabs
- Drag a tab out → creates new window
- Drag new window back → fails
- Drag tab between two windows → fails
Expected behavior
Reattach detached window as tab
Move tabs between windows
Additional information
This is unconsistent UX.
Nemo's tab drag-and-drop is a clear usability bug, not a missing feature. The app deliberately supports dragging a tab out to create a new window, which sets a strong user expectation for the reverse operation - dragging that window back to reattach as a tab. Blocking this bidirectional flow, along with tab movement between windows, breaks the fundamental promise of tabbed interfaces found in industry standards like Firefox, Chrome, and Windows Explorer etc.
This half-implementation frustrates natural workflows: users who detach a tab to compare folders expect to easily merge them back, not close and reopen everything. By teasing complete tab functionality but delivering a one-way street, Nemo creates cognitive dissonance that punishes the user, making it objectively harder to use than competitors with consistent UX.
Distribution
Mint 22.3
Package version
6.6.3
Frequency
Always
Bug description
I belive this is not "by design" - it's a usability regression. The normal behaviour is l support bidirectional tab movement. Nemo's half-implementation trains false expectations then punishes users.
Detached tabs/windows are "one-way" - no reattach/move.
Steps to reproduce
Open Nemo and create multiple tabs
Expected behavior
Reattach detached window as tab
Move tabs between windows
Additional information
This is unconsistent UX.
Nemo's tab drag-and-drop is a clear usability bug, not a missing feature. The app deliberately supports dragging a tab out to create a new window, which sets a strong user expectation for the reverse operation - dragging that window back to reattach as a tab. Blocking this bidirectional flow, along with tab movement between windows, breaks the fundamental promise of tabbed interfaces found in industry standards like Firefox, Chrome, and Windows Explorer etc.
This half-implementation frustrates natural workflows: users who detach a tab to compare folders expect to easily merge them back, not close and reopen everything. By teasing complete tab functionality but delivering a one-way street, Nemo creates cognitive dissonance that punishes the user, making it objectively harder to use than competitors with consistent UX.