New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot disable new ExposedDropdownMenuBox (it is not recomposed) #3686
Cannot disable new ExposedDropdownMenuBox (it is not recomposed) #3686
Comments
Hi @mahozad, thanks for reporting it
That's the main problem here -
The current behaviour is the same on Android (Google's Jetpack Compose), so issue came from there. Therefore it requires fixing not only in our fork. |
Thanks. |
## Proposed Changes - Update callback between recompositions in `ExposedDropdownMenuBox` This changes must be upstreamed ## Testing Test: run code snippet from JetBrains/compose-multiplatform#3686 ## Issues Fixed Fixes JetBrains/compose-multiplatform#3686
## Proposed Changes - Update callback between recompositions in `ExposedDropdownMenuBox` This changes must be upstreamed ## Testing Test: run code snippet from JetBrains/compose-multiplatform#3686 ## Issues Fixed Fixes JetBrains/compose-multiplatform#3686
## Proposed Changes - Update callback between recompositions in `ExposedDropdownMenuBox` This changes must be upstreamed ## Testing Test: run code snippet from JetBrains/compose-multiplatform#3686 ## Issues Fixed Fixes JetBrains/compose-multiplatform#3686
Describe the bug
I'm creating a custom exposed dropdown based on the new common one introduced in Compose Multiplatform 1.5.10-beta01.
It takes a parameter called
isEnabled
but cannot make the dropdown ignore clicks when theisEnabled
isfalse
.See https://stackoverflow.com/a/74534475/8583692.
exposed-not-disabled.mp4
Affected platforms
Select one of the platforms below:
Versions
To Reproduce
The text was updated successfully, but these errors were encountered: