M3 ModalBottomSheet - The keyboard does not open when clicking on a text field in the modal [272483584]

Fixed

Bug

Status Update

No update yet.

Description

b....@gmail.com

created issue #1

Mar 9, 2023 04:53PM

Jetpack Compose version: 1.3.3

Material 3 version : 1.1.0-alpha08

Jetpack Compose component used: ModalBottomSheet

Android Studio Build: #AI-221.6008.13.2211.9619390

Kotlin version: 1.8.0

Issue : If we add a text field in a modal. When clicking on the text field of the modal. The keyboard does not open. Once you close the modal, the keyboard opens.

Simple code :


val scope = rememberCoroutineScope()
val sheetState = rememberModalBottomSheetState()
Button(onClick = {
    scope.launch {
        sheetState.show()
    }
}) {
    Text("Open it")
}
if (sheetState.isVisible) {
    ModalBottomSheet(
        sheetState = sheetState,
        onDismissRequest = {
            scope.launch {
                sheetState.hide()
            }
        },
    ) {
        TextField(
            value = "",
            onValueChange = { },
        )
    }
}

Comments

dy...@gmail.com <dy...@gmail.com> #2Mar 9, 2023 06:27PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Louis Pullen-Freilich <lpf@google.com>
Link: https://android-review.googlesource.com/3328184

Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling

Expand for full commit details

Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling 
 
These APIs allow overscroll to have events dispatched to it by one component, and rendered in a separate component. 
 
Fixes: b/266550551 
Fixes: b/204650733 
Fixes: b/255554340 
Fixes: b/229537244 
Test: OverscrollTest 
Relnote: "Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling APIs - these APIs create a wrapped instance of the provided overscroll effect that doesn't draw / handle events respectively, which allows for rendering  overscroll in a separate component from the component that is dispatching events. For example, disabling drawing the overscroll inside a lazy list, and then drawing the overscroll separately on top / elsewhere." 
Change-Id: Idbb3d91546b49c1987a041f959bce4b2b09a9f61

Files:

M compose/foundation/foundation/api/current.txt
M compose/foundation/foundation/api/restricted_current.txt
M compose/foundation/foundation/integration-tests/foundation-demos/src/main/java/androidx/compose/foundation/demos/OverscrollDemo.kt
M compose/foundation/foundation/samples/src/main/java/androidx/compose/foundation/samples/OverscrollSample.kt
M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/OverscrollTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/Overscroll.kt

Hash: f64e25b7a473c757d080521e7dd97b3f6670f60d
Date: Fri Nov 01 18:43:56 2024

ta...@gmail.com <ta...@gmail.com> #3Mar 10, 2023 12:00PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.foundation:foundation:1.8.0-alpha06
androidx.compose.foundation:foundation-android:1.8.0-alpha06
androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha06
androidx.compose.foundation:foundation-linuxx64stubs:1.8.0-alpha06

se...@google.com <se...@google.com> #4Mar 10, 2023 04:48PM

I have somewhat tracked down the issue here and

https://issuetracker.google.com/268380384

In the other bug, the underlying popup is not set as focusable, so the keyboard opens. In alpha08 we have set the popup as focusable to intercept focus when the popup opens for A11y purposes. However it has the unintended consequence of intercepting ime actions, for some reason not passing them to child content despite the content (like textfield) still being focusable... Working on a solution.

se...@google.com <se...@google.com> Mar 13, 2023 12:39PM

Accepted by se...@google.com.

lx...@gmail.com <lx...@gmail.com> #5Mar 16, 2023 09:55AM

I find a way to make TextField editable for me. you can make a try.

ModalBottomSheet(/* .... */) {
    
    // add follow code here to make your text filed edtable.
    val view = LocalView.current.rootView.allViews
                    .filter { it.javaClass.name == "androidx.compose.ui.window.PopupLayout" }
                    .toList()
                    .first()
    (view.context.getSystemService(Context.WINDOW_SERVICE) as WindowManager)
                    .updateViewLayout(view,
                        (view.layoutParams as WindowManager.LayoutParams).apply {
                            flags = flags and WindowManager.LayoutParams.FLAG_NOT_FOCUSABLE.inv()
                        })
    
    // your bottom sheet content code
    TextField(/* ... */)
}

mr...@gmail.com <mr...@gmail.com> #6Apr 13, 2023 06:19PM

Has anyone found any way to fix this?

se...@google.com <se...@google.com> #7Apr 19, 2023 04:55PM

This issue which extends to any custom windows seems to have been resolved with: https://issuetracker.google.com/262140644

Waiting on that change to land to proceed on this issue.

ap...@google.com <ap...@google.com> #8Apr 20, 2023 03:00PM

Project: platform/frameworks/support
Branch: androidx-main

commit 7545cec3617ab5d1ea83d66822bc094e7f03c562
Author: José Figueroa Santos <serniebanders@google.com>
Date: Wed Apr 19 16:04:18 2023

[Material3][gradle] Update compose dependencies to 1.4.2

Upgrade needed to intake the following bug fix:

b/262140644

, which resolves issue of new windows not calling IME keyboard.

Bug: 268380384
Bug: 272483584
RelNote: ModalBottomSheet now can display IME keyboard
Test: Manual
Change-Id: Idc5082008acb547cac2100a69cab4be7db85f50f

M compose/material3/material3/build.gradle
M compose/material3/material3/samples/src/main/java/androidx/compose/material3/samples/BottomSheetSamples.kt

https://android-review.googlesource.com/2548352

se...@google.com <se...@google.com> Apr 20, 2023 03:01PM

Marked as fixed.

za...@gmail.com <za...@gmail.com> #9Apr 22, 2023 02:28PM

It doesn't seem to be fixed for me. I used a snapshot build from androidx.dev (9991820) which has the updated dependencies, but the keyboard still doesn't show up when a text field is focused. It also no longer shows up once the bottom sheet is dismissed, so something did change, but not enough.

se...@google.com <se...@google.com> #10Apr 24, 2023 05:51PM

@ Comment#9 what device and API are you using.

za...@gmail.com <za...@gmail.com> #11Apr 24, 2023 06:26PM

I tested on a Pixel 7 running Android 14 Beta 1 and a Galaxy S23 Ultra running Android 13, both with Gboard.

When I tap a text field, it focuses and the cursor shows up, but the text scrubber handle also appears and is aligned to the top of the field instead of below the text.

za...@gmail.com <za...@gmail.com> #12May 13, 2023 12:31AM

It seems to be fully fixed in 1.2.0-alpha01.

ju...@google.com <ju...@google.com> #13May 24, 2023 07:37PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.material3:material3-android:1.2.0-alpha02

ty...@udisc.com <ty...@udisc.com> #14Jun 25, 2023 03:01PM

Is this fix going to be back ported to 1.1? Seems like 1.2 alpha 2 does fix the issue but also introduces other issues such as the sheets not respecting system bars, some issue with insets always being zero unless you enable "edge to edge" mode.

va...@gmail.com <va...@gmail.com> #15Jan 18, 2024 03:41PM

there are couple of concerns related to the behavior of the BottomSheet in Jetpack Compose and its subsequent versions:

Overlapping with System Navigation Button:
Version 1.1.0 effectively resolves the issue of the BottomSheet overlapping with the system navigation button.
However, in versions above 1.1.0, including 1.2 alpha2, the BottomSheet reintroduces the problem of overlapping with the system navigation button.

TextField Click Behavior and Keyboard Activation:
The keyboard activation works fine in higher versions (1.2 alpha-2). However, the primary concern remains with the overlapping issue in these higher versions, which requires attention.

Seeking a comprehensive fix that addresses the overlapping with the system navigation button in higher versions, while acknowledging the keyboard activation improvement. Your attention to this matter would be highly appreciated.

Issue 272483584

Description

Issue summary

Comments

dy...@gmail.com <dy...@gmail.com> #2Mar 9, 2023 06:27PM

ta...@gmail.com <ta...@gmail.com> #3Mar 10, 2023 12:00PM

se...@google.com <se...@google.com> #4Mar 10, 2023 04:48PM

se...@google.com <se...@google.com> Mar 13, 2023 12:39PM

lx...@gmail.com <lx...@gmail.com> #5Mar 16, 2023 09:55AM

mr...@gmail.com <mr...@gmail.com> #6Apr 13, 2023 06:19PM

se...@google.com <se...@google.com> #7Apr 19, 2023 04:55PM

ap...@google.com <ap...@google.com> #8Apr 20, 2023 03:00PM

se...@google.com <se...@google.com> Apr 20, 2023 03:01PM

za...@gmail.com <za...@gmail.com> #9Apr 22, 2023 02:28PM

se...@google.com <se...@google.com> #10Apr 24, 2023 05:51PM

za...@gmail.com <za...@gmail.com> #11Apr 24, 2023 06:26PM

za...@gmail.com <za...@gmail.com> #12May 13, 2023 12:31AM

ju...@google.com <ju...@google.com> #13May 24, 2023 07:37PM

ty...@udisc.com <ty...@udisc.com> #14Jun 25, 2023 03:01PM

va...@gmail.com <va...@gmail.com> #15Jan 18, 2024 03:41PM

Add comment

Issue metadata