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)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
[ID: 84651]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides.
See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 746686]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides. See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 920908]
[ID: 966373]
[ID: 966375]
[ID: 966382]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
Jetpack Compose version: 1.4.2
Jetpack Compose component used: Modifier.focusRequester, Modifier.focusGroup(), Column, Box
Android Studio Build: not applicable
Kotlin version: 1.7.20
Android TV & moving focus using D-Pad
Code Sample:
Expected behaviour:
enter = {}
should be triggered and selected focusRequester should be focusedWhat happens:
enter = {}
is triggered and correct Box is selected, each next focus enter does not trigger this scope and the default behaviour is triggered. Only on first attempt with FocusRequester different than Default when we exit focus using d-pad the Column scope ofexit = {}
is triggered and correct Box is selected, each next focus exit does not trigger this scope and the default behaviour is triggered.enter/exit = { FocusRequester.Default }
scope is triggered every time