yonlu/yellowjacket
1
1
Fork 0
Code Issues 55 Pull Requests 6 Actions Packages Projects Releases 12 Wiki Activity

Desktop: track list column configuration should be reachable from the track list, not only from Settings #39

New Issue
Open
opened 2026-08-18 05:57:03 +00:00 by logan · 0 comments
logan commented 2026-08-18 05:57:03 +00:00
Collaborator
Copy Link
Copy Source

Report

The column configuration currently living in Settings should be accessible from the Tracks list itself.

Findings

  • The columns are persisted config (tracklist.DefaultColumns in Go; DEFAULT_COLUMN_IDS in frontend/src/components/track-list/columns.ts is what the list draws until the config arrives — the two must agree).
  • Column widths are already edited in place by dragging the header handles, and loadColumnWidths is keyed by column id.
  • The phone layout uses a fixed PHONE_COLUMN_IDS set with no headers at all, so a header-anchored control must be desktop-only, and the page header's sort list is built from configuredColumns.

Direction

A "Columns" control on the track list — right-click the header row, or a button in page-header's actions — writing the same config Settings writes. Keep the Settings panel or remove it, but not two editors that can disagree: one component, two mount points.

**Report** The column configuration currently living in Settings should be accessible from the Tracks list itself. **Findings** - The columns are persisted config (`tracklist.DefaultColumns` in Go; `DEFAULT_COLUMN_IDS` in `frontend/src/components/track-list/columns.ts` is what the list draws until the config arrives — the two must agree). - Column widths are already edited in place by dragging the header handles, and `loadColumnWidths` is keyed by column id. - The phone layout uses a fixed `PHONE_COLUMN_IDS` set with no headers at all, so a header-anchored control must be desktop-only, and the page header's sort list is built from `configuredColumns`. **Direction** A "Columns" control on the track list — right-click the header row, or a button in `page-header`'s actions — writing the same config Settings writes. Keep the Settings panel or remove it, but not two editors that can disagree: one component, two mount points.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Area/Design
Area/Downloads
Area/Explore
Area/Library-UI
Area/Metadata
Area/Packaging
Area/Player
Area/Queue
Area/Settings
Area/Shell-Nav
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Platform/Android
Platform/Desktop
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
In Progress
Somebody is actively working on this right now
No labels Area/Library-UI Area/Settings Kind/Enhancement Platform/Desktop
Priority
Medium
3
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
logan yonlu
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yonlu/yellowjacket#39