Chris Keenan

I haven't had time to test #134 yet, but if it works and no one has any objections I'll close this pull request upon #134 merge.

Thanks for bringing this up. I'll try and take a look at this tonight and see if I can track down the issue. Please test on the latest version as...

@lepicekmichal I have tested on a Pixel 3a emulator with API 31 (Android 12) and I wasn't able to reproduce the issue. Can you provide some additional context to help...

Relevant Android source code: **ArrayMap:** https://android.googlesource.com/platform/frameworks/base/+/27f592d/core/java/android/util/ArrayMap.java **Parcel.readArrayMapInternal:** https://android.googlesource.com/platform/frameworks/base/+/27f592d/core/java/android/os/Parcel.java#2303

@lepicekmichal Without any more information, and being unable to reproduce this issue, there's no way to solve it. Also, what do you mean by "bad shift"? The code is open...

I will consider this when I have time, thanks

Has anyone fixed this issue yet? I am facing a similar problem. When the FloatingActionsMenu is collapsed, the FloatingActionButtons onClick is being called when the screen is touched above the...

A simple solution I came up with was to manually set each FloatingActionButton's visibility when the FloatingActionsMenu expanded or collapsed. ``` Java actionMenu.setOnFloatingActionsMenuUpdateListener(new FloatingActionsMenu.OnFloatingActionsMenuUpdateListener() { @Override public void onMenuExpanded() {...

@wakaztahir Thanks for bringing up the issue. A few things here: * You do not need to use the `SingleNavigationContext` constructor. The logic for that is encapsulated within the library....

@wakaztahir Yes, a simple, easy to use API is one of the main goals of this library. And that is why I am considering removing the `NavigationContext` concept altogether as...