The current behaviour is somewhat strange ... if you have content fitting on screen and use a flickable, the content is going to scroll offscreen and bounce back ... shouldn't it rather do nothing? (it's easy to trigget scrolling by mistake when trying to interact with the UI)
In ubuntu-system-settings we worked around the behaviour by using "boundsBehavior: Flickable.StopAtBounds" in our flickables, but that's changing the scrolling behaviour when panels don't fit on screen
The issue was discussed on IRC and we are now changing to boundsBehavior: (contentHeight > mainPage.height) ? Flickable.DragAndOvershootBounds : Flickable.StopAtBounds
We agreed it would be good to have a bug to discuss the default behaviour and see if we need that changed in the toolkit, so here we go... ;-)
The current behaviour is somewhat strange ... if you have content fitting on screen and use a flickable, the content is going to scroll offscreen and bounce back ... shouldn't it rather do nothing? (it's easy to trigget scrolling by mistake when trying to interact with the UI)
In ubuntu- system- settings we worked around the behaviour by using "boundsBehavior: Flickable. StopAtBounds" in our flickables, but that's changing the scrolling behaviour when panels don't fit on screen
The issue was discussed on IRC and we are now changing to
boundsBehavio r: (contentHeight > mainPage.height) ? Flickable. DragAndOvershoo tBounds : Flickable. StopAtBounds
We agreed it would be good to have a bug to discuss the default behaviour and see if we need that changed in the toolkit, so here we go... ;-)