Compose artifacts release day! 🎉 Looks like a mostly perf focussed release IMO 1.5.0-beta01 • Removed allocations in recomposition, color animations, spring animations and

AndroidComposeView

(Ie9431) and (Ib2bfa) • Reduce allocations during lazy list/grids/etc. measurements (Iaf9e2) • Reduced allocations when applying snapshots (I65c09) • Removed allocations from spring animations (Ie9431) • Removed allocation from

TextLayout

(I0fd11) • Removed multiple allocations in pointer velocity tracking (I26bae) • Reduced allocations (I65c09, d7ea77, 727974, and 445808 ) • Reduced allocations in layout and pointer input management (I5333a) • Optimize Vector memory usage and first-frames rendering (I2f3c6) • Removed allocations when drawing lines and points with Canvas (I9f535) • Improved performance and reduce allocations in Vector APIs (I906cb) • Added a color parameter to

BasicText

to allow efficiently animating or setting text color. (Iffd88, b/246961787) • Added a color parameter to

BasicText

to allow efficiently animating or setting text color. (Iffd88, b/246961787) • Don't retain snapshot reference in

ComposerImpl

(0206f7) • Quick cancellation of compose

CoroutineScopes

(a55362 and bd382f) • Don’t apply composition twice (f5791b) • Ensure invalidation for non-initialized derived state values (aa2a92) • Call

onEndChanges

during composition dispose. (62cc8c) • Fix moving content into a sub-composition (4beb41) • Fix potential deadlocks (c1a425 • ON_STOP should pause the frame clock broadcasts instead of composition (f4a2d1) • Fix changed flags for restarted lambdas (8a03e9) • Execute deactivation callbacks for

LayoutNode

before disposing effects (8b0fa4) • Bunch of api changes, nothing tooooo crazy, but maybe just worth taking a look at this URL https://developer.android.com/jetpack/androidx/releases/compose-ui#1.5.0-beta01 • Implement

PlatformDataProvider

to provide heart rate and daily steps.

SensorGateway

interface is removed from the public API. (I55b84) material 1.5.0-beta01 • `DrawerState`'s and `BottomDrawerState`'s offset are not nullable anymore. They instead return

Float.NaN

to indicate the absence of the offset. (Ie9855) • Added an option to pass in a

ScrollState

when constructing a

DropdownMenu

or an

ExposedDropdownMenu

for controlling the vertical scroll state of the displayed menu items. (Idb009, b/185304441) • Add the support for enabling/disabling the gesture of

ModalBottomSheetLayout

so that user could configure this for more featured bottomsheet (I40af0) • Added a color parameter to

BasicText

to allow efficiently animating or setting text color. (Iffd88, b/246961787) • Renaming the Semantics property

isContainer

to

isTraversalGroup

(I121f6) • Fixed the

AlertDialog

dismiss action to appear below the confirm action when the actions stacked over each other to fit into the dialog's width. This fix align the implementation with the Material Design spec. (I029de, b/235454277) material3 notes in the 🧵

tested these latest versions, and all of the `ComponentDialog`/`ModalBottomSheet` keyboard regressions are finally fixed 😛arty-parrot:

I was just testing the scenarios I reported with m3 bottomsheets, still broken in all the cases I reported (they're broken differently/not all the way fixed).

M3 Modal sheets are finally usable, yay!

There are multiple issues in tracker but this is the one I created from issues found in our testing - https://issuetracker.google.com/274872542 M3 ModalBottomSheet content behind / overlaps navigation bar in many scenarios

😱