** Description changed:
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
+ 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... ;-)
+
+ Design solution:
+ If flickable content does not exceed the available space, it should not flick
at all.
** Changed in: ubuntu-ux
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201394
Title:
[SDK] the flickables should only be active if there is enough content
for scrolling
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1201394/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
