I am using 'com.android.support.constraint:constraint-layout:2.0.0-alpha5'. I have a fragment using MotionLayout inside an activity that also carries a BottomNavigationView inside a CoordinatorLayout with a custom behaviour allowing to show and hide when the content is scrolled. With all fragments, where there is no MotionLayout, this behaviour works perfectly. Only with the MotionLayout, which has a NestedScrollView as a child, and makes use of an onSwipe transition, this swipe seems to be consumed, and does not arrive at the activity's coordinator layout. Is this a current limitation of how MotionLayout works, and is it possible to extend it to support my use case?
Asked
Active
Viewed 518 times
0
-
were you able to solve this? – rlinoz Apr 29 '20 at 13:19
-
If I remember correctly, I did not find a solution, I had given up the experiments with MotionLayout. – mtotschnig Apr 29 '20 at 15:36