IssueTracker

Forgot to add a sample code! Here it goes:

SelectionContainer {
    LazyColumn {
        items(100) {
            Text("Line number $it")
        }
    }
}

A normal column works without any issues (expected since everything is composed unlike the LazyColumn).

Edit to give more details about my use case: I'm trying to show the lines of a text document in my app, so using a column is not an option as the files can be quite large.

Sean, would you be able to take the first stab at it and see what's needed?

This happens because the nodes containing selection are removed from the composition when they're scrolled out of view, which causes the selection container to stop tracking them. This is one of the use cases for b/195049010.

b/195049010 has been fixed, we can now request items be pinned to stay composed even when not visible. We just need to update BasicText to pin itself when it's participating in selection.

It'd be interesting to test how it can affect performance when selecting large number of lines.

Confirmed that the text field is actually getting focus from the effect, so this is definitely an IME issue and not a focus one.

Is there a workaround for this? The issue happens for components that are a part of androidx.compose.ui.window.Popup as well.

I get the following error when a BasicTextField component within a Popup requests focus:

Ignoring showSoftInput() as view=androidx.compose.ui.platform.AndroidComposeView{50b009a VFED..... .F....ID 0,0-1079,2218} is not served.

And the keyboard doesn't show.

When I try to force the keyboard to show using

val imm: InputMethodManager =
    LocalContext.current.getSystemService(Context.INPUT_METHOD_SERVICE) as InputMethodManager
imm.toggleSoftInput(InputMethodManager.SHOW_FORCED, 0)

I see that the keyboard renders behind the Popup component (In my case the contents of the Popup take up a good portion of the screen).

Is there no way to control the Z axis of the contents of my Popup to show behind the system keyboard?

Or is it just not recommended to have a text input field inside a Popup at all?

Also experiencing the same issue (1.4.0-alpha04) as #8 regarding soft keyboard showing behind dialog and so keys cannot be pressed. Any workaround?

EDIT: note, I'm using com.google.android.material.dialog.MaterialAlertDialogBuilder and setting the content view with a ComposeView

Also still experiencing this. On compose 1.3.1. Dumb workaround is to use a delay(100).

A more robust workaround that worked for me was waiting for window focus.

val windowInfo = LocalWindowInfo.current

LaunchedEffect(windowInfo) {
    snapshotFlow { windowInfo.isWindowFocused }.collect { isWindowFocused ->
        if (isWindowFocused) {
            focusRequester.requestFocus()
        }
    }
}

Any update on this? Experiencing this in M3 and Compose 1.6.

Causes our UI tests to fail about 20% of the time since our UI tests are written with the keyboard open and thus when it's not causes scrolling and assertion issues.

This should be fixed in 1.7.

Can you link to the commit where this was fixed? I'm interested in the implementation that fixes this. Also, is the fix available in 1.7.0-beta02 release?