https://bugs.kde.org/show_bug.cgi?id=387797
Bharadwaj Raju <bharadwaj.raju...@protonmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bharadwaj.raju777@protonmai
| |l.com
--- Comment #27 from Bharadwaj Raju <bharadwaj.raju...@protonmail.com> ---
(In reply to Nate Graham from comment #20)
> Even a basic QtQuickControls 2 ScrollView still has this behavior. Still
> have not found what exactly is triggering it, whether that is something deep
> in Qt or a thing we are overlaying on top of it in Plasma-land.
It's in QML ListView. It scrolls the view to move the current item into view.
The docs say:
"If highlightFollowsCurrentItem is true, setting either of these properties
will smoothly scroll the ListView so that the current item becomes visible."
However, it seems like the scrolling happens even if
highlightFollowsCurrentItem is false.
I've tried messing around with custom highlight size and positioning, but
haven't got a solution that way.
> QQC2 apps that have ListView inside ScrollView do not seem to suffer from
> this issue.
Because QQC2 list delegates generally don't set currentIndex on hover. Plasma's
*ListItem components do.
We could probably make it so that hovering doesn't change currentIndex but only
highlights, but that would make it so that there can be two highlighted items
visible, with one of them being the actual current item and the other only a
hover. But the idea is worth discussing, maybe we can have the
hovered-but-not-current highlight be more subtle/subdued etc.
--
You are receiving this mail because:
You are watching all bug changes.
