Header sorting replaces the overview sort dropdown; files Owner and Tags sortable (#786) #796
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat-786"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #786.
Overview: the
.spovsortselect is removed (markup, wiring, CSS). Name / Members / Storage used / State headers are.hsortbuttons — same markup,FB_ARRarrows and.onaccent state as the files header; the.hsortCSS is extended to.spovtblinstead of duplicated. One comparator parses the stored"<column>-<dir>", so values saved by the old dropdown stay valid. Defaults: Name/State ascending, Members/Size descending; repeat click toggles. State sorts by the chip label alphabetically (commented); ties fall back to name (case-insensitive, numeric-aware). Tiles follow the stored sort.spovSort/spovSortMembersi18n keys kept (qa783 key-pins them).Files: Owner and Tags headers become
hsortbuttons;fbCmpsorts owner by display name and tags by the alphabetically first tag, with empties last in both directions; alpha columns default ascending; the sort button gains honest labels (Owner A–Z/Z–A, Tags A–Z/Z–A ×4 languages) instead of falling back to "Name A–Z".Pins updated deliberately: qa743 (Tags header markup) and qa783's dropdown test.
Verification: RED → splice → 279/279. Both comparators were executed in Node against sample data extracted from the spliced file — every ordering (both directions, empties, ties, legacy pref) checked. Header styling previewed on the live overview before pushing.