Bug 504296 - Remember sort direction separately for each sorting criterion, like Windows Explorer
Summary: Remember sort direction separately for each sorting criterion, like Windows E...
Status: RESOLVED DUPLICATE of bug 471331
Alias: None
Product: dolphin
Classification: Applications
Component: view-engine: general (other bugs)
Version First Reported In: unspecified
Platform: Manjaro Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-15 21:56 UTC by Tito
Modified: 2025-05-19 17:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tito 2025-05-15 21:56:20 UTC
Currently, when sorting files in Dolphin, the sort direction (ascending/descending) is remembered globally and applied to all sorting criteria.
For example, if I sort files by "Date Modified" and switch to descending (newest first), then switch back to sorting by "Name", the files are sorted in reverse alphabetical order (Z → A), which is usually not what the user expects.

In Windows Explorer, the sort direction is remembered per criterion. That means:

    Sorting by name defaults to ascending (A → Z),

    Sorting by date defaults to descending (newest first),

    And switching between them remembers the last used direction per criterion.

This behavior is much more intuitive and useful, as users typically want:

    Recent files first when sorting by date,

    Alphabetical order when sorting by name.

Dolphin’s current behavior is technically consistent, but less user-friendly.

Suggestion: Implement a mechanism to store and recall sort direction per sort criterion, or at least use more intuitive defaults (e.g., date = descending by default).

Thank you for considering!
Comment 1 John Kizer 2025-05-19 17:20:53 UTC
Hi - merging this in with the existing request for this feature, thanks!

*** This bug has been marked as a duplicate of bug 471331 ***