Obsolete
Status Update
Comments
fa...@google.com <fa...@google.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?
ay...@google.com <ay...@google.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
ma...@google.com <ma...@google.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
al...@gmail.com <al...@gmail.com> #5
Could you please check the attached project as we couldn't extract the files from it.
ck...@google.com <ck...@google.com>
ma...@google.com <ma...@google.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.
al...@google.com <al...@google.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.
Description
Hey Farheen. While reviewing material API and talking about ListItem api, it made sense to us to expect a Surface inside of ListItem, meaning that ListItem is non-transparent and has some background.
However, according to specs (go/material-params), this is not the case and ListItem should have no background and obey the parent background and content-color wise.
I if this scales and works in real apps, as usually it's expected that ListItem has a background. For example:
Given that both 1 and 2 are very common patterns in material, I wonder if material ListItem that we make in compose should also provide Surface underneath by default.
Looking for your opinion and guidance. Thanks!