You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Given a Compose Web app with a TextField, if it is accessed through a browser using a mobile phone, clicking on a text field does not open the software keyboard.
The TextField is receiving the focus as the labelmoves to the top side.
Affected platforms
Web (K/Wasm) - Canvas based API - Accesing with a mobile device
Versions
Compose Multiplatform version: 1.6.6
Kotlin version: 1.9.23
Device (model or simulator for iOS issues): Nothing Phone - Google Chrome App
To Reproduce
Steps to reproduce the behavior:
Download a new project using the Compose Multiplatform Wizard
Set the App() content to this:
@Composable
fun App() {
MaterialTheme {
var input by remember { mutableStateOf("") }
Box(
Modifier.fillMaxSize(),
contentAlignment = Alignment.Center
){
TextField(
modifier = Modifier,
value = input,
label = { Text("Label") },
onValueChange = { input = it }
)
}
}
}
Run the "wasmJsBrowserRun" gradle task, or other related local deployment task.
Enter the web through a browser using a smart phone
Click on the TextField
Expected behavior
The software keyboard should be displayed.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Given a Compose Web app with a TextField, if it is accessed through a browser using a mobile phone, clicking on a text field does not open the software keyboard.
The TextField is receiving the focus as the labelmoves to the top side.
Affected platforms
Versions
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The software keyboard should be displayed.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: