Where there some changes to LazyLists flings and touch inputs in recent 1.7 alphas ? I can't find a ...

# compose

[Tolriq]

Where there some changes to LazyLists flings and touch inputs in recent 1.7 alphas ? I can't find a commit, but now it seems if you start a fling then touch the list again to keep scrolling a detectDragGesturesAfterLongPress can now get called while it was not the case before.

[Albert Chang]

https://android-review.googlesource.com/c/platform/frameworks/support/+/2957875

[Tolriq]

Wow ok so this is normal, this is quite a big UX change. Do you understand the " and there will be more benefits to having the original behavior without the issues the fix introduced." as the original behavior that will be restored is the continuing the scroll will again intercept?

[Tolriq]

I workarounded with

pointerInput(lazyGridState.isScrollInProgress) {
        if (!lazyGridState.isScrollInProgress) {
            detectDragGesturesAfterLongPress(

But the restart of the pointInput is less efficient 😞

[Tolriq]

Hum actually that one is quite old and was in alpha 3, the issue appears on very recent changes. (After 11763555)

[Tolriq]

From the dates and what that other pr changes I suspect https://github.com/androidx/androidx/commit/0176b61c4ea0088f26809830a9f647c52050c423 we really need a tool for non Googler to match CL and snapshotIds to bisect and help reporting 😞

[Albert Chang]

I’m not sure what your setup is but if a list is flinging and you long press it (so the fling stops), having detectDragGesturesAfterLongPress called seems like the correct behavior to me.

[Tolriq]

The issue is you fling, then touch and scroll with your finger largely passing the touchSlop, but the detectDragGesturesAfterLongPress is called while it should not and never did. If you long press without moving then yes it would be normal, here's it's triggering during the second scroll.

[Albert Chang]

then touch and scroll with your finger

If you mean scroll immediately without long press, then this definitely doesn’t look right and you should file an issue. If you mean scroll after a long press, I would say starting a new gesture seems more correct to me.

[Tolriq]

Yes I mean scroll immediately. This was never an issue in ages before a very recent snapshot. Now quite a few users face this so it's definitely an unwanted change. https://issuetracker.google.com/issues/338786473

[Tolriq]

And you can tell by my workaround that there's something odd since the gesture should not start when it's scrolling.