Touch slop should be taken into account before dispatching nested pre scroll [139530818]

Fixed

Bug

Status Update

No update yet.

Description

je...@google.com

created issue #1

Aug 16, 2019 03:33PM

dispatchNestedPreScroll is called without waiting for the touch slop, which means that unintended movement might occur.

In the worst case it can make it very hard to scroll in the perpendicular direction of the direction in which pre-scroll is consumed, because as soon as pre scroll starts consuming, nested scrolling (should) lock the scroll in that direction.

Comments

je...@google.com <je...@google.com> Aug 20, 2019 02:53PM

Accepted by je...@google.com.

ap...@google.com <ap...@google.com> #2Aug 22, 2019 01:52PM

I guess technically, the ProGuard rule should be on androidx.work.NonBlockingWorker subclasses, but I'd also be okay with just not using reflection to access the Worker(Context, WorkerParamters) constructor and skipping the need for a ProGuard rule at all.

je...@google.com <je...@google.com> Aug 28, 2019 05:22PM

Marked as fixed.

Issue 139530818

Description

Issue summary

Comments

je...@google.com <je...@google.com> Aug 20, 2019 02:53PM

ap...@google.com <ap...@google.com> #2Aug 22, 2019 01:52PM

je...@google.com <je...@google.com> Aug 28, 2019 05:22PM

Add comment

Issue metadata