Status Update
Comments
lb...@gmail.com <lb...@gmail.com>
vi...@google.com <vi...@google.com> #2
Hi, thanks for reporting this. For now this is expected as nested scrolling is only activated through gesture based scrolling, not animation based scrolling. We do have plans to explore animation based nested scrolling in the future, so I'll keep you posted if things change. Closing this ticket for now as this is WAI.
vi...@google.com <vi...@google.com> #3
Is there a ticket to follow?
lb...@gmail.com <lb...@gmail.com> #4
xt...@live.com <xt...@live.com> #5
Can we add a ticket for animation based nested scrolling? So it can at least be tracked publicly.
Its not possible to workaround this when the nestedScroll(connection, null)
modifier is hidden deep in 3rd party code.
Also it sort of weird too as one needs to manually call all nested scroll methods (pre & post scroll) & actual component scrolling methods, effectively reimplementing ScrollingLogic
, somewhat.
xt...@live.com <xt...@live.com> #6
I second this, or at least the trackable issue for animation based nested scrolling
Description
Thing is, it doesn't mention QUERY_ALL_PACKAGES permission at all, and the Play policy team is stuck on the idea that it's not needed for this purpose.
The QUERY_ALL_PACKAGES is required on Android 13 and below for this purpose, and Google already admitted it here:
Now the Play policy insists that I should not use it.
Please tell them to be in sync with the real situation, and let apps have this permission for this purpose, at least if they offer to be installed on Android 13 and below.