Fixed
Status Update
No update yet.
Comments
st...@gmail.com
I have the same problem. I hope this issue gets resolved quickly.
st...@gmail.com
I'm having the same problem, which makes this a dealbreaker for using it unfortunately.
sg...@google.com
sg...@google.com
ap...@google.com
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.
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.
sg...@google.com
st...@gmail.com
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(/* ... */)
}
sg...@google.com
Has anyone found any way to fix this?
Description
Jetpack Compose version: 1.2.0-alpha03
Jetpack Compose component used: androidx.compose.material3:material3
Android Studio Build: N/A
Kotlin version: N/A
DatePickerState used to be a public class, now in 1.2.x it is an interface. Before I was constructing an instance of this class in a state holding class (as described in the docshttps://developer.android.com/jetpack/compose/state#managing-state )
Now I can no longer do that, since DatePickerStateImpl is private, and the only exposed way to construct one with the rememberDatePickerState(), which is a composable function.
I feel like it should not only be possible to construct those state objects in composition. Hoisting this state into my own state holder has been super useful to be able to control the state there, and have the composables themselves use the state as it is, without constructing it and dealing with logic like which dates are allowed etc. and simply emit the UI as it should be.
Can this scenario please be considered? The docs that I linked above even are the ones who promote the idea of having these state holders, so the material3 library disallowing it for specifically the date picker component feels quite out of place.