Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
Jetpack Compose version: Compose BOM 2024.09.03
Material Library Version (M2, M3 or Both?): M3, v1.3.0
Material Compose component used: androidx.compose.material3.Scaffold
Android Studio Build: Android Studio Koala Feature Drop | 2024.1.2 Patch 1
Kotlin version: 2.0.21
Description
The default focus order of a scaffold using both a topBar and a bottomBar seems incorrect and prioritises the bottomBar over the content. The focus is now initially placed on the topBar navigation icon, then goes to the bottomBar and lastly the content. The expected order would be topBar -> content -> bottomBar, similar to the order talkback uses.
Below code snippet renders a minimal reproduction of the issue.
When no
navigationIcon
is provided in the topBar, the initial focus is placed on the first button in the content (Button 0). In this case, the scaffold does seem to follow the "logical" focus order: button 0 -> button 1 -> button 2 -> bottom left -> bottom right.Attached videos show the issue described.
Sample code: