Bug 496956 - The intensity with which a selection is highlighted is not directly the right one
Summary: The intensity with which a selection is highlighted is not directly the right...
Status: RESOLVED INTENTIONAL
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.08.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-02 20:29 UTC by Sikal
Modified: 2024-12-15 07:29 UTC (History)
2 users (show)

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


Attachments
Video of the problem (64.40 KB, video/mp4)
2024-12-02 20:29 UTC, Sikal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sikal 2024-12-02 20:29:03 UTC
Created attachment 176301 [details]
Video of the problem

SUMMARY
When an item is selected in Dolphin (file, folder, etc.), the highlighting on first click is darker. On the second click, the highlighting returns to its normal intensity.

STEPS TO REPRODUCE
1. Open Dolphin
2. Click one time on any folder or file
3. Click a second time to see the difference 

OBSERVED RESULT
A darker highlighting than expected

EXPECTED RESULT
The lighter highlighting like after the second click 

SOFTWARE/OS VERSIONS
Linux: 6.12.1-arch1-1
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8
Qt Version: 6.8
Comment 1 John Kizer 2024-12-13 07:01:06 UTC
Hi - this is reflecting where the keyboard focus is in Dolphin. When clicking a location in the Places panel, the keyboard focus is initially put in the main view of that directory - so for example, arrow keys will navigate up and down through the files and directories shown.

When clicking that same location a second time, the keyboard focus then stays in the Places panel, since there's no change being made to the directory being displayed - so for example, arrow keys will navigate up and down through the Places in that panel.

Hope that helps,
Comment 2 Sikal 2024-12-15 07:29:06 UTC
I'm sorry to have opened this bug.
Thanks for the explanations!