Obsolete
Status Update
Comments
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com> #2
frameworks/support/compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/Chip.kt
ty...@gmail.com <ty...@gmail.com> #3
Project: platform/frameworks/support
Branch: androidx-main
commit 50a35b0cda0a79d7cfb0d5db8a00462b49f02b3e
Author: Connie Shi <connieshi@google.com>
Date: Mon Oct 30 12:59:10 2023
Make the constructor for `ChipElevation` and `SelectableChipElevation` public.
Bug: 308432421, 307583745
Test: Ran existing tests.
Relnote: "Make the constructor for `ChipElevation` and `SelectableChipElevation` public."
Change-Id: Ie0c48d7eec6b96d0276d434ed91ad94e53ad6a6c
M compose/material3/material3/api/current.txt
M compose/material3/material3/api/restricted_current.txt
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/Chip.kt
https://android-review.googlesource.com/2810534
Branch: androidx-main
commit 50a35b0cda0a79d7cfb0d5db8a00462b49f02b3e
Author: Connie Shi <connieshi@google.com>
Date: Mon Oct 30 12:59:10 2023
Make the constructor for `ChipElevation` and `SelectableChipElevation` public.
Bug: 308432421, 307583745
Test: Ran existing tests.
Relnote: "Make the constructor for `ChipElevation` and `SelectableChipElevation` public."
Change-Id: Ie0c48d7eec6b96d0276d434ed91ad94e53ad6a6c
M compose/material3/material3/api/current.txt
M compose/material3/material3/api/restricted_current.txt
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/Chip.kt
ku...@google.com <ku...@google.com> #4
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
[Deleted User] <[Deleted User]> #5
Hello. What is the status of this issue?
ad...@google.com <ad...@google.com>
am...@google.com <am...@google.com> #6
The issue reported here has been fixed. Please check on the latest version and report back if the issue persists.
ru...@gmail.com <ru...@gmail.com> #7
This issue was first entered in 2014 and it still persists...........
I wonder what version #6 is referring to, because I'm running my app on the latest and I still can see this problem.
Please, provide more info before changing the status!!!
I wonder what version #6 is referring to, because I'm running my app on the latest and I still can see this problem.
Please, provide more info before changing the status!!!
na...@gmail.com <na...@gmail.com> #8
Still not working. Tested on Google Pixel 4A Emulator latest API.
cl...@gmail.com <cl...@gmail.com> #9
It's also not working here in an app with target and compile sdk 34 (tested on pixel 6 / sdk 34)
Description
This issue is a copy of an existing issue (36996315), but has to be refiled. According to a Google developer at Google I/O 2018 the bug's status probably got 'lost' when switching bug trackers for Android. The bug is still relevant, hasn't been solved (even though it's marked as Obsolete).
ORIGINAL REPORT:
- Steps to reproduce the problem (including sample code if appropriate).
Create a simple layout with a spinner and set any value for the dropDownHorizontalOffset attribute
For example -
<Spinner
android:id="@+id/spinner"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_centerInParent="true"
android:dropDownHorizontalOffset="50dp"
android:prompt="@string/spinner_title"
android:spinnerMode="dropdown" />
- What happened.
The dropdown popup window is displayed normally without any horizontal offset.
- What you think the correct behavior should be.
The dropdown popup window should be applied the horizontal offset *before* displaying it.
A quick dive in the Spinner source code revealed that though the horizontal offset is being applied to the popup window in the Spinner's constructor, it is not being taken into consideration in the computeContentWidth() which is called before displaying the spinner. Thereby causing the popup window to not have the proper horizontal offset.
Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).
Nexus 10 4.4.2
ADDITIONS:
As can be seen in the comments on the original issue, this issue still exists and is still relevant.