Split off from #52. The three M3 Expressive FAB composables are not present in Xamarin.AndroidX.Compose.Material3 1.4.0.3 — only design tokens (FabMediumTokens, ExtendedFabMediumTokens) ship, no actual composable classes. They land upstream in androidx.compose.material3:material3:1.5.0-alpha* (or via the separate material3-expressive preview artifact, which we don't reference per the bindings policy).
Blocked on a newer NuGet
| Composable |
Kt class |
Status in 1.4.0.3 |
MediumFloatingActionButton |
FloatingActionButtonKt |
not in binding |
FloatingActionButtonMenu |
FloatingActionButtonMenuKt |
not in binding |
FloatingActionButtonMenuItem |
FloatingActionButtonMenuKt |
not in binding |
ToggleFloatingActionButton |
ToggleFloatingActionButtonKt |
not in binding |
Track a Xamarin.AndroidX.Compose.Material3 1.5.x update; once it's published, the work is the same shape as #52 — [ComposeBridge] partials + [ComposeDefaults] enums (or generated bindings, if dotnet/java-interop#1440 has landed by then).
FloatingActionButtonMenu is multi-child (FloatingActionButtonMenuItem children), so it'll be a ComposableContainer-shape facade.
Why split
#52 is being narrowed to the three FAB variants we can do today (Small/Large/Extended) so it can ship against the current Material3 NuGet without waiting on Expressive.
Split off from #52. The three M3 Expressive FAB composables are not present in
Xamarin.AndroidX.Compose.Material31.4.0.3 — only design tokens (FabMediumTokens,ExtendedFabMediumTokens) ship, no actual composable classes. They land upstream inandroidx.compose.material3:material3:1.5.0-alpha*(or via the separatematerial3-expressivepreview artifact, which we don't reference per the bindings policy).Blocked on a newer NuGet
MediumFloatingActionButtonFloatingActionButtonKtFloatingActionButtonMenuFloatingActionButtonMenuKtFloatingActionButtonMenuItemFloatingActionButtonMenuKtToggleFloatingActionButtonToggleFloatingActionButtonKtTrack a
Xamarin.AndroidX.Compose.Material31.5.x update; once it's published, the work is the same shape as #52 —[ComposeBridge]partials +[ComposeDefaults]enums (or generated bindings, if dotnet/java-interop#1440 has landed by then).FloatingActionButtonMenuis multi-child (FloatingActionButtonMenuItemchildren), so it'll be aComposableContainer-shape facade.Why split
#52 is being narrowed to the three FAB variants we can do today (Small/Large/Extended) so it can ship against the current Material3 NuGet without waiting on Expressive.