Assigned
Status Update
Comments
as...@gmail.com <as...@gmail.com> #2
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?
fr...@gmail.com <fr...@gmail.com> #3
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
yo...@gmail.com <yo...@gmail.com> #4
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
je...@google.com <je...@google.com>
av...@gmail.com <av...@gmail.com> #5
Could you please check the attached project as we couldn't extract the files from it.
ja...@gmail.com <ja...@gmail.com> #6
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.
pa...@gmail.com <pa...@gmail.com> #7
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.
za...@gmail.com <za...@gmail.com> #8
@ coordinator layout,
Please check this issue and provide your inputs.
Please check this issue and provide your inputs.
da...@gmail.com <da...@gmail.com> #9
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?
Description
The issue is basically this one:
which also have images
<CoordinatorLayout>
<AppBarLayout/>
<fragment or content or whatever/>
<BottomNavigationView/>
</CoordinatorLayout>
You need to set
app:layout_behavior="@string/appbar_scrolling_view_behavior"
on your content view to make itself position below the appbar and behave well (I'm assuming the content has both with/height as match_parent)
but if you add a BottomNavigationView with gravity bottom it will overlap your content.
I wanted to set:
app:layout_insetEdge="bottom"
on the BottomNavigationView
and
app:layout_insetEdge="bottom"
which makes your content stay above the BottomNavigationView but then your content end up behind the appbar.
The only solutions to this I've found involve putting another layout in the mix, for example a LinearLayout containing content and bottom. But this means you can't rely on proper behavior of insets dodging (you'd ideally want a snackbar to pop up ABOVE the BottomNavigationView and your content to dodge it).
The content should actually "resize", not just offset.
Am I missing something? --> is there a doc about this?
Is this intended behavior? --> can you fix it?
thanks