Assigned
Status Update
Comments
se...@google.com <se...@google.com>
za...@gmail.com <za...@gmail.com> #2
Hello, can you please attach a sample that reproduces your error?
ni...@gmail.com <ni...@gmail.com> #3
I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally,
Description
Jetpack Compose version: 1.7.0
Material Library Version (M2, M3 or Both?): M3
Material Compose component used: material3-compose
Android Studio Build: N/A
Kotlin version: 2.0.0
Currently, https://issuetracker.google.com/issues/292204649 ), and more. I'd like to use
ModalBottomSheet
is only usable with itsPopup
(and sometimesDialog
?)-based impl. While I understand the motivation given that this is an easy way to stack UIs on top, not every app needs this and the imposition of aPopup
/Dialog
has significant collateral effects. They're frankly quite janky in many cases, keep changing between releases, often have small bugs with configuration changes (ModalBottomSheet
within my existing compose UI hierarchy and do have UI architecture that supports arbitrary overlays like this.So, I'd like to feature request extraction of the implementation. In principle, I think this is simple. Take everything passed into the
content
param forModalBottomSheetPopup
and move it to a separate, top-level public API.Note that just copying these contents and doing it ourselves isn't really viable, as almost all of material3 's implementations rely heavily on non-reusable internal APIs (seehttps://proandroiddev.com/opinion-jetpack-compose-needs-a-design-system-layer-dc579fde79b2 ).