Why Do Kirigami Scrollable Pages Misbehave with Nested Flickable Areas on Plasma Mobile?

Development
1

Hello

I am building a Plasma Mobile app using Kirigami & I have run into an issue with nested Flickable & ScrollView components. :slightly_smiling_face:On desktop it behaves correctly; but on Plasma Mobile (tested on PinePhone and emulator), nested scrollable sections become unresponsive / jittery. For eg; placing a vertical list inside a Kirigami.ScrollablePage with another Flickable (like an image carousel or interactive section) causes either the parent / the child scroll area to break. :innocent:

I have experimented with manually setting interactive: false and boundsBehavior; but it feels like Plasma Mobile handles input propagation differently than desktop environments. :upside_down_face:

This becomes especially frustrating in forms or hybrid UIs where both scroll and swipe gestures are essential. Is there a recommended pattern for nesting Flickable / ListView within a ScrollablePage that avoids these input conflicts? :thinking: I checked Kirigami - KDE Community Wiki guide reated to this and found very helpful. Also checked what is Cloud Computing guide while working on an app.

Any guidance; sample code / insight into how Plasma Mobile handles touch & gesture events differently than KDE desktop would be appreciated. :innocent:I would love to make this app as fluid as possible for mobile users without breaking desktop compatibility.

Thank you !! :slightly_smiling_face:

2

I didn’t know that page existed :smiley:

Our Kirigami docs are in Getting started with Kirigami | Developer

Can you show the source code? Both Scrollable pages and list views | Developer and ScrollablePage QML Type | Kirigami warn you not to use ScrollView in a ScrollablePage, but maybe that’s not what you mean there.