Bug 486278

Created attachment 168989 [details]
Shows the bug in dolphin, in KDE Neon running inside KVM

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
By default, file/folder names in dolphin are centered. When a file is renamed, the selected text remains centered, however as soon as some text is entered, the entire file name becomes left aligned. Upon renaming, when focus is removed (by pressing enter or clicking somewhere else), the text aligns back to centered. If filename is deleted, then the cursor remains at the left edge instead of being centered.

STEPS TO REPRODUCE
1. Select some file, use F2 or right click> rename
2. Input some text
3. The filename aligns to the left.

OBSERVED RESULT
The file/folder name aligns to left while editing name.

EXPECTED RESULT
The file/folder name should be centered.

SOFTWARE/OS VERSIONS
Tested on (live booted in KVM, neon-testing-20240423-0253.iso ):
Operating System: KDE neon Testing Edition
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 8.1 GiB of RAM
Graphics Processor: virgl
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

Also on:
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 17.5 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook_ASUSLaptop X512DA_X512DA
System Version: 1.0

ADDITIONAL INFORMATION
- Dolphin version is 24.02.2 for both KDE Neon and Fedora 40.
- Also, this bug report has an attachment showing similar behaviour but I'm not sure if the objective of that report is similar to this one. If it's the same, apologies to the triaging folks for duplicate :-/