Assigned
Status Update
No update yet.
Comments
cs...@supercharge.io
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What is the expected output?
Current output
What is the current output?
co...@google.com
ma...@google.com
gs...@gmail.com
How can you possibly need more information, i just told you the exact part of code causing the issue, and the code changes required to fix it!
Please read the description.
Expected output:
What is the expected output?
See attached "expected.webm" video in OP
Current output
What is the current output?
See attached "actual.webm" video in OP
Please read the description.
Expected output:
What is the expected output?
See attached "expected.webm" video in OP
Current output
What is the current output?
See attached "actual.webm" video in OP
co...@google.com
1. Import attached project
2. Install and run on Android 5 (Lollipop) or above
3. Click FAB and see it fall below/behind the navigation bar once the Snackbar disappear
2. Install and run on Android 5 (Lollipop) or above
3. Click FAB and see it fall below/behind the navigation bar once the Snackbar disappear
sk...@gmail.com
Could you please check the attached project as we couldn't extract the files from it.
ni...@gmail.com
It's a RAR archive, there's no issue with it.
However you have problems extracting such, here's the same content as a ZIP archive.
However you have problems extracting such, here's the same content as a ZIP archive.
ka...@gmail.com
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.
aj...@gmail.com
@ coordinator layout,
Please check this issue and provide your inputs.
Please check this issue and provide your inputs.
ya...@gmail.com
This is still an issue in 1.2.0. Looks like nobody at Google uses FABs with Snackbars in CoordinatorLayout? How can such obvious issue be still present after more than 3 years?
jo...@gmail.com
This seems to work around the issue successfully:
snackbar.addCallback(object : Snackbar.Callback() {
override fun onDismissed(transientBottomBar: Snackbar?, event: Int) {
transientBottomBar?.removeCallback(this)
Handler(Looper.getMainLooper()).post {
coordinatorLayout?.requestApplyInsets()
}
}
})
ro...@gmail.com
Having bottom sheets as destinations will help with reusability of M3 bottom sheets which is getting more stable. Considering this can we have an update here ?
aj...@gmail.com
Any update here??
ey...@gmail.com
as...@gmail.com
Here's a working solution I've created based on Google's
Feel free to import this as a module compose-material3-navigation
Make sure to:
val bottomSheetNavigator = rememberBottomSheetNavigator()val navController = rememberNavController(bottomSheetNavigator)ModalBottomSheetHost(bottomSheetNavigator)beforeNavHost()
Description
Please create an artifact for Material 3 as well.