Bug 508134 - When scrolled down in the list of network so that top of expanded details is not visible, moving up cursor does not highlight
Summary: When scrolled down in the list of network so that top of expanded details is ...
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (other bugs)
Version First Reported In: 6.4.4
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-11 20:56 UTC by tomashnyk
Modified: 2025-08-12 12:14 UTC (History)
1 user (show)

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


Attachments
Notice the cursor above the details but without highlight (52.21 KB, image/png)
2025-08-11 20:56 UTC, tomashnyk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tomashnyk 2025-08-11 20:56:20 UTC
Created attachment 183968 [details]
Notice the cursor above the details but without highlight

SUMMARY


STEPS TO REPRODUCE
1. Open the applet and expand details on the highest item
2. Scroll down so that top of the expanded details with the name of the network is not visible anymore
3.  Move the cursor to second entry and then back up to the first.

OBSERVED RESULT
1. The expanded details entry is not highlighted.

EXPECTED RESULT
1. The expanded details entry is highlighted.

(would this qualify as a 15 minute bug?)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-08-11 20:58:47 UTC
I can confirm this. It seems like a quirk of the way ListView highlights managed by the ListView work in QML. Once the actual list item is out of the view, QML unloads it even if its expanded area is visible, so there's no highlight effect.

There isn't a clean Qt change that could be made to resolve this without breaking other things even worse, so I think we have to live with it, sorry.
Comment 2 tomashnyk 2025-08-11 21:03:30 UTC
It is not a big deal, yes,however, should it not be marked as RESOLVED>UPSTREAM? Sounds like a Qt issue.
Comment 3 Nate Graham 2025-08-12 12:14:32 UTC
It's ambiguous whether it's an issue in Qt or not. It's the intended design. But sure, any changes would need to happen there, so we can mark it as UPSTREAM.