[sdk] Cannot change boundsBehaviour on Flickable in Expandable

[Jonas G. Drange]

Right now it's quite unfortunate that some Expandables can be dragged and overshot (Flickable.DragAndOvershootBounds).

Could the Expandable expose the boundsBehaviour property or in some other way make this changeable?

UX Solution:
We should have a good default, then allow developers to change the property.

For example, an app developer might not want to have overshoot at all and provide a different hint that the list/area boundaries have been reached.

https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#bookmark=id.7h7o4x6hs2ql

[Tim Peeters (tpeeters)]

I would say we need a good default settings, and we don't need to expose the property.

Would a default that prevents overshooting work for you?

[Tim Peeters (tpeeters)]

and what do the ux designers think about it?

[Jonas G. Drange (jonas-drange)]

Tim, preventing overshooting would work for my case, but maybe not other cases where an expandable contains text/content that you might want to overshoot.

[Giorgio Venturi (giorgio-venturi-deactivatedaccount)]

I think we should have a good default, then allow developers to change the property.

For example, an app developer might not want to have overshoot at all and provide a different hint that the list/area boundaries have been reached.