Fixed
Status Update
Comments
ca...@google.com <ca...@google.com>
ap...@google.com <ap...@google.com> #2
Thank you for your patience, we have rolled back a change in the Google 3D Tiles API service. Could you check on your end if this fixes your issue?
ca...@google.com <ca...@google.com>
ap...@google.com <ap...@google.com> #3
Thank you for your prompt response and for rolling back the recent change
in the *Google 3D Tiles API service*. I have tested it on my end, and I can
confirm that the issue is now resolved.
I truly appreciate your quick action in addressing this matter. Your
support is invaluable, and I'm grateful for the efficiency and dedication
of your team.
Thanks again for your help!
*Best regards,Mohammad*
On Fri, Feb 14, 2025 at 7:17 AM <buganizer-system@google.com> wrote:
in the *Google 3D Tiles API service*. I have tested it on my end, and I can
confirm that the issue is now resolved.
I truly appreciate your quick action in addressing this matter. Your
support is invaluable, and I'm grateful for the efficiency and dedication
of your team.
Thanks again for your help!
*Best regards,Mohammad*
On Fri, Feb 14, 2025 at 7:17 AM <buganizer-system@google.com> wrote:
Description
Version used: 1.1.0-alpha02
Theme used: Theme.AppCompat.Light.DarkActionBar
Devices/Android versions reproduced on: Samsung Galaxy Note8 (Android 8.0.0)
When scrolling through the items of a spinner (slowly), it keeps automatically jumping back to the previously selected item. This makes scrolling (almost) impossible. See attached screen recording and sample project.
This is a new issue since appcompat 1.1.0-alpha02. The previous alpha01 has no issues. It looks like this is the commit which broke the spinner:
Before this commit, because mPopupContext would be null, the framework implementation of SpinnerPopup was used which does not have this issue. This commit changed some stuff, so now the AppCompat implementation of SpinnerPopup is always used. However, it looks like this has some scrolling bugs on Android Oreo. So it could be that this issue was already there in the AppCompat implementation of SpinnerPopup previously.
- Relevant code to trigger the issue: See attached sample project.
- A screenrecord or screenshots showing the issue (if UI related): See attached screenrecord.