Status Update
No update yet.
Comments
he...@samsung.com
Thanks for providing all the details we need! We've accepted this issue and will fix this in an upcoming release.
Join our discussion group (
Please note that you have submitted this information with the knowledge that we may use, modify, reproduce, publicly display, and distribute the information in accordance with our open source policies. Please let us know if you did not intend to submit the information for such use.
an...@google.com
he...@samsung.com
Since Android P (API level), auto focusing has been disabled. In contrast, Android O (API level) supports the auto focusing feature.
```
Starting from Android P (API level 28), focus management has become more strict. This change aims to improve user experience, security, and stability. Here are the key focus policy changes in Android P:
1. **Focus Chain Limitation**: In Android P, the focus chain is no longer allowed to expand indefinitely. Instead, the focus chain is limited to a maximum of 6 views. This helps prevent performance issues that can occur when the focus chain becomes too long.
2. **Focus Order**: In Android P, the focus order is no longer determined automatically. Instead, developers must explicitly specify the focus order. This helps prevent unexpected focus movements for users.
3. **Focus Attributes**: In Android P, the `focusable` and `focusableInTouchMode` attributes are no longer set automatically. Instead, developers must explicitly set these attributes. This helps prevent unnecessary focus movements.
4. **Focus Change Events**: In Android P, focus change events no longer occur automatically. Instead, developers must explicitly handle focus change events. This helps prevent unexpected focus movements for users.
These changes allow developers to have more control over focus management, which can improve user experience, security, and stability.
To improve focus management in Android P, consider the following:
- **Limit the focus chain**: Make sure the focus chain is not too long. Split the focus chain if necessary.
- **Specify the focus order**: Explicitly specify the focus order to prevent unexpected focus movements.
- **Set focus attributes**: Explicitly set the `focusable` and `focusableInTouchMode` attributes to prevent unnecessary focus movements.
- **Handle focus change events**: Explicitly handle focus change events to prevent unexpected focus movements.
By considering these changes and improvements, you can enhance user experience, security, and stability in your Android P applications.
```
ra...@google.com
Yes, this is working as intended. Prior to API 28, we assign initial focus even in touch mode. More details at
Description
Jetpack Compose component(s) used: ui
Android Studio Build: *
Kotlin version: *
Steps to Reproduce or Code Sample to Reproduce:
1. This is only occurred since OREO (API 27)
2. set Modifier::focusable with interactionSource
3. check collectAsFocusState
4. it return true wheher user don't touch anything.
below is a code snippets reproducible.
```
val interactionSource = remember { MutableInteractionSource() }
val focused = interactionSource.collectIsFocusedAsState()
Column(
modifier = Modifier
.focusable(enabled = true, interactionSource = interactionSource)
.clickable(indication = null, interactionSource = interactionSource) { },
verticalArrangement = Arrangement.spacedBy(8.dp)
) {
Text(text="focused ${focused.value}")
repeat(100) {
Text(text = "test$it",
modifier = Modifier.height(100.dp).fillMaxWidth()
.background(Color.Gray))
}
}
```
Stack trace (if applicable):
```
<add stack trace here>
```