Status Update
Comments
ma...@google.com <ma...@google.com> #2
Branch: androidx-master-dev
commit 23a7d960caf43390a554700d3c56ada189a9d10e
Author: Louis Pullen-Freilich <lpf@google.com>
Date: Mon Aug 10 15:11:36 2020
IconButton / IconToggleButton API scrub
Test: ./gradlew updateApi
Bug:
Bug:
Relnote: "Adds enabled parameter to IconButton, and reorders parameters in IconToggleButton"
Change-Id: I0a9419b1a631cadad451395302ad87b7f9214f96
M ui/ui-material/api/current.txt
M ui/ui-material/api/public_plus_experimental_current.txt
M ui/ui-material/api/restricted_current.txt
M ui/ui-material/src/commonMain/kotlin/androidx/compose/material/IconButton.kt
co...@google.com <co...@google.com> #3
se...@google.com <se...@google.com> #4
I think it's worth noting in M2 that ModalBottomSheet is a layout while bottomdrawer functions more as a truly modal object, even though it does not have perfect dialog-like functionality. For the usecase recommended (bottom app bar menus), BottomDrawer seems like a better fit than ModalBottomSheetLayout. However in M3 it makes sense to explicitly use ModalBottomSheet once implemented.
Wdyt Matvei?
ma...@google.com <ma...@google.com> #5
I think it's worth noting in M2 that ModalBottomSheet is a layout while bottomdrawer functions more as a truly modal object
Could you comment on that? What's the actual difference in the behaviour?
se...@google.com <se...@google.com> #6
Bottom Drawer is an atomic component that can be placed on top of content on the screen while ModalBottomSheet is a layout that wraps around all the screen content and places accordingly. BottomDrawer is much more of a splashable component in M2 and asking users to migrate BottomDrawer uses may be cumbersome.
ma...@google.com <ma...@google.com> #7
Ok, sounds good. I'm happy to keep it if you think it brings value to m2 users.
If we are not removing it, we need to make it stable in this case.
se...@google.com <se...@google.com>
se...@google.com <se...@google.com> #8
Found some outstanding bugs I will look into before deciding to promote, especially the swipeable migrations which will likely update the API
se...@google.com <se...@google.com> #9
Given the planned work to migrate the swipeable logic of bottomdrawer, this API should remain experimental. Closing for now.
cl...@google.com <cl...@google.com> #10
If these are still experimental, please keep this bug open and just target the next release
se...@google.com <se...@google.com> #11
Where can i find the respective hotlist for the next release?
se...@google.com <se...@google.com>
jo...@google.com <jo...@google.com> #12
Fwiw the major difference between modal sheets and bottom drawer is that the drawer can be opened by swiping on the full container. If we don't intend to introduce a bottom drawer in M3, maybe we can explore how to adapt the ModalBottomSheet API for this feature in the future.
ma...@google.com <ma...@google.com> #13
Bumping to P1 as it is been a long while since we need to land this.
mo...@google.com <mo...@google.com> #14
This is an out-of-SLO bug that is assigned to me. Moving to Matvei to ensure that it is looked at.
ap...@google.com <ap...@google.com> #16
Branch: androidx-main
commit 63b8ceee3645b3d78a2c372f01390937bf14c8bd
Author: Jossi Wolf <jossiwolf@google.com>
Date: Wed Nov 29 15:17:04 2023
[M2] Stabilize BottomDrawer
Relnote: BottomDrawer has been promoted from experimental to stable. BottomDrawerState now exposes the progress as a function, allowing to query progress between specific targets. BottomDrawerState now allows customizing the animation spec, and confirmStateChange is not a trailing lambda anymore.
Fixes: 261423850
Test: Existing tests, bottomDrawer_progress
Change-Id: I9c029340ea69a755ad0cd8f46b8fcdc76422c41c
M compose/material/material/api/current.txt
M compose/material/material/api/restricted_current.txt
M compose/material/material/src/androidInstrumentedTest/kotlin/androidx/compose/material/DrawerTest.kt
M compose/material/material/src/commonMain/kotlin/androidx/compose/material/Drawer.kt
pr...@google.com <pr...@google.com> #17
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material:material:1.7.0-alpha03
androidx.compose.material:material-android:1.7.0-alpha03
androidx.compose.material:material-desktop:1.7.0-alpha03
Description
The following Experimental APIs have existed for several releases.
Please consider stabilising or removing these APIs: