:loudspeaker: :compose: All Compose users, please ...

# compose

[darkmoon_uk]

📢 ✏️ All Compose users, please consider voting for this issue in the google Issue tracker

I know everyone wants their issue voted for - but really... this is a big one!
If you have ever or will ever put a TextField inside a scrollable area then this affects you.

Currently, Compose does not maintain visibility of focused elements inside a scrollable viewport, when it shrinks.
This affects the very common case, where a user taps a Text Field and keyboard pops up. Often the field will become hidden behind the keyboard due to the viewport not scrolling (this is not an Activity adjustResize or Insets issue).

Currently the only workaround is a hacky solution with a delay and RelocationRequester.
This needs a proper solution!

[adjpd]

This is the biggest Compose issue for me.

Any bottom-located BasicTextField in a lazyColumn will be obscured by the keyboard.

Compose's lazyColumn / BasicTextField behaviour doesn't match Android's RecyclerView / EditText behaviour to the point where it seriously hinders the user's experience.

[Adam Powell]

please don't instigate vote brigading like this. We're well aware of this use case and it's already prioritized accordingly. Thanks for linking the bug so that folks can follow along though 🙂

[Sanjeeviraj M]

is this fixed in any alpha or beta version?
i have tried using adjustResize, it opens the keyboard, the keyboard appears overlaps input text, and then keyboard closes.

[darkmoon_uk]

There's no solution to this yet, it will probably require a design-level fix with new or enhanced API's. I don't think it's really an implementation bug.

[jw]

Don't do that. You are abusing both the direct mention and send to channel feature.

[dimsuz]

...and the issue tracker too. I understand that issues can be frustrating and feel important, but often not as much as you feel in the heat of the moment 🙂

For example this is for sure a very broad claim you've made on an issue tracker:

it makes compose unusable

How come we are about to release a major banking app with UI written purely in Compose, if Compose is unusable? 😉

It may be unusable in you case and I even suspect this is the case for some specific screen. You can work around that if you wish. Use RecyclerView for example.