Status Update
No update yet.
Comments
su...@google.com
su...@google.com
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.
ka...@gmail.com
Is there a ticket to follow?
ra...@google.com
lb...@gmail.com
co...@gmail.com
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.
co...@gmail.com
I second this, or at least the trackable issue for animation based nested scrolling
Description
I didn't mention getWallpaperInfo anywhere there.
Also, this is incorrect or at least not documented anywhere :
"Apps that seek to process the current wallpaper image should prompt the user to select the wallpaper image from their media storage."
No Intent exists to let the user choose the current wallpaper of lock/home-screen, so that the app could fetch it without any kind of permission.
The only way to get the current wallpaper is by using WallpaperManager :
The issue here is about MANAGE_EXTERNAL_STORAGE permission. This permission is required when targeting Android 13. There is no way to avoid it.
Please talk with the policy team so that you will both be in sync about this matter.
Only this way they will be flexible about having this permission for this purpose, as a minimized permission isn't available yet.