Bug 485328

Summary: Files in folder view widget not consistently highlighted/clickable, mostly in "list view"
Product: [Plasma] plasmashell Reporter: Michael Bromilow <dev>
Component: Desktop icons & Folder View widgetAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: hein, nate
Priority: NOR    
Version: 6.0.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Michael Bromilow 2024-04-10 14:54:51 UTC
***
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
When mousing over items in a folder view widget, they are not consistently highlighted and clickable, as though they are losing focus.

STEPS TO REPRODUCE
1. Add "folder view" widget to panel, pointing to somewhere with a few files/folders.
2. Configure "Icons/View Mode" as "List" (the default).
3. Move cursor up and down list of files/folders.

OBSERVED RESULT
Sometimes the cursor is on top of items and they are not highlighted; clicking has no effect.

EXPECTED RESULT
The item that the cursor is hovering over should be highlighted and clickable at all times.

SOFTWARE/OS VERSIONS
Arch Linux (confirmed in a fresh VM)
KDE Plasma: 6.0.3
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Using Wayland KWin session.

ADDITIONAL INFORMATION
Seems to have some link to changing the direction of the cursor up/down. It also happens in Icon view but is hard to notice as it seems the larger size of the icons causes the highlighting to kick in after some amount of movement.

I believe this regression occurred between 5.27 and 6.0; unfortunately I am currently short on time to investigate exactly where further.
Comment 1 Nate Graham 2024-04-10 15:56:38 UTC

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