Version 1.2.0-alpha03 released! Lots of really in...

# compose

[Colton Idle]

Version 1.2.0-alpha03 released!

Lots of really interesting changes and welcome bug fixes!!!

Here are interesting bits from releases notes and commit messages (in my opinion)
• TextFields will now be kept above the keyboard when they are focused and the keyboard is shown, when the soft input mode is ADJUST_RESIZE. (I8eaeb, b/190539358, b/192043120)
• Bunch of more commits regarding input field focus although I think the main bug on issuetracker is not technically fixed yet
• Window inset modifiers?! Not sure exactly what this means yet, but I do wonder if this makes accompanist-insets unnecessary?
• Debounce restart input commands in TextInputServiceAndroid (I believe this fixes the "flash" on the keyboard when moving from one input field to another)
• "Support content types in Lazy lists" ("Providing such information helps item composition reusing logic to make it more efficiently and only reuse the content between the items of similar type.")
• Oh. Yep to the above ^ "The soft keyboard input type no longer flickers when changing focus between text fields. (I1bf50, b/187746439)"
• Lots of things related to text field magnification? (I gotta admit, I'm not sure exactly what this is but theres a bunch of commits about it) /shruggie
• New scrollable chip group sample added
• New material 3 components (DropdownMenu, DropdownMenuItem, Card, OutlinedCard, ElevatedCard)
• Added movableContentOf which converts a composable lambda into a lambda that moves it state, and corresponding nodes, to any new location it is called. When the previous call leaves the composition the state is temporarily preserved and if a new call to the lambda enters the composition then the state, and associated nodes, are moved to the location of the new call. If no new call is added the state is removed permanently and remember observers are notified.
• Added a tracing API to composition to enable tools to provide more detailed tracing of composable functions. The compiler now generates calls to the tracing API which include source information. (Ib0eb5) This apparently adds required/optional (not sure) proguard rules? -assumenosideeffects public class <http://androidx.compose.runtime.Com|androidx.compose.runtime.Com>...
• Add InternalComposeScope which gives tools the ability to identify a composable during recompositions. (I07a3f)
• Fix bug when rememberSaveable with input is restored in the wrong order
• A bunch of changes regarding Fonts
• A bunch of things regarding MPP and Robolectric
• Also, I didn't see this in release notes, but it seems like it was fixed according to issue tracker "Add material decoration box for TextField and OutlinedTextField/ Provide a way to remove the extra horizontal padding from TextField It allows additionally to what is customisable in text fields already to customise paddings (incl. for dense text field support), border or indicator line."

[Zach Klippenstein (he/him) [MOD]]

That should have said ADJUST_PAN, my bad. Working on fixing the release notes now. Sorry.

[Colton Idle]

Accompanist insets docs seem to suggest that adjustResize is needed. Any issue there?

[Ben Trengrove [G]]

Yes, window insets will take over from accompanist insets

[Zach Klippenstein (he/him) [MOD]]

Yea you probably never actually want to use adjust_pan lol. But if you do for some reason, it should be inconvenient in the correct way 😅

[jasu]

My note text is still going below keyboard, using the latest compose ui version(alpha03), tried adjusting pan and resize but no luck. any idea? @Zach Klippenstein (he/him) [MOD] @Colton Idle

I’ve a below hierarchy
Column
-Title TextFiled
-Note TextFiled

[Zach Klippenstein (he/him) [MOD]]

Can you share your code?

[jasu]

Yeh @Zach Klippenstein (he/him) [MOD] here it is

[jasu]

note text is going below the keyboard.
expected behaviour:
1. If you keep typing, last line should always on top of keyboard
2. If i paste some long text and keyboard is open again the last line should be above the keyboard
actual behaviour: In both cases text goes below the keyboard

Note edit screen.kt

[Zach Klippenstein (he/him) [MOD]]

Please file a bug, and if you could also attach a screen recording that would be ideal

[Siyamed]

I love what @Colton Idle does 🙂