Bug 432786

Summary: in Details Mode, "modified date" field is not consistent, see attachments
Product: [Applications] dolphin Reporter: Safeer Pasha <safeerpasha7>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: kfm-devel, nate
Priority: NOR    
Version: 20.12.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: "modified date" inconsistency

Description Safeer Pasha 2021-02-11 07:55:27 UTC
Created attachment 135590 [details]
"modified date" inconsistency

SUMMARY

the date in the "modified date" field in "Details Mode" is not aligned properly.

see the attachment screenshot.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-02-11 17:02:19 UTC
The date test is aligned left. If we aligned it to the right, it would be mis-aligned on the other side. Or are you saying that the date should be left-aligned and the time should be right-aligned? If we did that, then there would be a big gap between them if the column was quite wide.

Can you clarify what you see the problem as and which of these solutions you would prefer?
Comment 2 Safeer Pasha 2021-02-14 07:44:04 UTC
(In reply to Nate Graham from comment #1)
the problem lies in the date format. it should be two digits even when one digit would suffice.
like this: 14/02/21 not: 14/2/21. 
if the format is fixed, the alignment will get fixed automatically. 

i did some research and i think this it is not Dolphin's fault. it about locale and the date format used in the locale.
Comment 3 Nate Graham 2021-02-16 16:30:32 UTC
That's correct. The locale formatting is controlled ultimately by you the user, in the Formats page in System Settings. :)

Unfortunately the UX for changing it is pretty horrible, but that's tracked with Bug 394698.