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
Assign issue to yourself
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
Android API version: Android API 35
Material Library version: Material 3 Android Library BOM 2024.11.0 (1.3.1)
Device: Pixel 7, Android 15
Problem
I have the following design:
I have a
NavHost
inside the content of the navigation drawer. When I'm on top-most screen and I open the drawer, the predictive back collapsing the drawer works fine. Predictive back works. However, when I navigate to another screen (e.g. using a menu item on the drawer) which has the drawer also available, and open drawer FROM that other screen - then the Back gesture goes back to the main screen instead of closing the open drawer. Back gesture hides the drawer only if navigation has nothing to go back to.NavHost
is lower in the hierarchy, and it is its back handler that is checked first, not the drawers despite it taking 90% of the screen.If I put a custom
BackHandler
inside the Scaffold content:then drawer is closer as expected, before navigation, but the predictive back of course doesn't work.
Actual behavior:
Back gesture navigates back keeping the drawer open.
Expected behavior:
If drawer is open, back gesture should first close the nav drawer and use predictive back animation.