Is there a way to prevent child composables from being focused, through the parent?

# compose

[Zoltan Demant]

Is there a way to prevent child composables from being focused, through the parent?

[Zoltan Demant]

My child composable has Modifier.focusRequester(x) and requestFocus() is called when its rendered (in a LaunchedEffect). As expected.. it gets the focus.

Now my parent composable overlays the child composable, but the keyboard still shows up. Ideally Id like to have something akin to how I block touch events.

private fun Modifier.disableInteractions(): Modifier {
    return pointerInput(Unit) {
        awaitPointerEventScope {
            while (true) {
                awaitPointerEvent(Initial).run {
                    changes.forEach(PointerInputChange::consume)
                }
            }
        }
    }
}

Ive tried overriding LocalFocusManager with a noop one, and LocalSoftwareKeyboardController with null; but the keyboard still shows up. I suspect Ill need to create a way to block the entire Modifier.focusRequester(x) part as well. Is there an easier way to go about it?

[Zoltan Demant]

Ultimately ended up creating a val LocalFocusEnabled: CompositionLocal<Boolean> that I check before requesting focus. Would I have loved a better way? Yes. Does it work? Yes. If anyone knows a better approach, please enlighten me 😃

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

I think this should do it:

Modifier.focusProperties { canFocus = false }

[Zoltan Demant]

It works for the focus itself but the keyboard still shows up as a result of the disabled focus, maybe bug?

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

So you have a text field under this modifier, which doesn’t get focus, but it still shows the keyboard?

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

BasicTextField2 or the old one?

[Zoltan Demant]

Yes, old one

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

Can you file a bug with a minimal reproducer?

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

If the field is showing the keyboard while not focused, that’s definitely a bug

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

Oh you know what it might be https://issuetracker.google.com/301477279

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

But still a text field bug, so please file

[Zoltan Demant]

Will du tomorrow 💪🏽

[Zoltan Demant]

It was a bit more complicated to repro than I thought, but here it is 😃 Apparently linked to input fields in lazy layouts, I tested BasicTextField2 as well - but same exact behavior there too!

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

I suspect this has nothing to do with text but a bug in the focus system, or modifiers, so i’m not surprised