Roberto Leinardi

Is there a link to the upstream bug that we can subscribe to?

For anyone else coming here looking for a fix, this is yet another "temporary" solution that implements the Navigator-level API solution (just remember to set `skipHalfExpanded` to `true`): ```kotlin @ExperimentalMaterialNavigationApi...

Hi @JasonEtco, thanks for your reply. I will be happy to contribute with some PR but I don't have any experience in developing GitHub Apps. Is there an easy way...

Hi Matt, porting your code to Android Things should be relatively easy since probably you just need to provide an interface for your SPI/I2C/GPIO device classes that is then used...

Hi @kiewietn, sorry for the late reply, busy week at work. This is definitely an improvement but I'm still afraid that people will not understand this limitation and will keep...

@fernandomantoan I'm not aware of any other solution. The bug seems to happen only on API 31+. It seems definitely an upstream bug, most probably on `com.google.android.material:material`.

I'm opening an issue on the material component library, I can reproduce the issue with just this simple layout: ``` ```

I have opened an issue upstream, please consider giving it a :+1: for visibility: https://github.com/material-components/material-components-android/issues/2617

Doesn't seem related since is not involving `com.google.android.material:material` nor API 31+.

Are you really sure you don't have the issue? I can still reproduce it without the `app:useCompatPadding="true"`, if I use the `app:fabSize="mini"`:  ``` ``` Repro branch available here: https://github.com/leinardi/FloatingActionButtonSpeedDial/tree/issue-2617