Drawer should close automatically when navigating to a new screen

Open Beginner friendly
#628 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
dart, flutter
Domain
mobile-dev

Research direction

Start at the drawer navigation handlers for Profile, Reports, and Settings, since the issue identifies those menu paths but no files or tests. Reproduce the navigation flow in the app, then verify that tapping a drawer item closes it and that returning home shows the main content without the drawer covering it.

Written by the indexing model from the issue text.

Description

bug
Describe your issue

When navigating to sections like Profile, Reports, or Settings from the side drawer, the drawer does not close automatically. This causes it to remain open in the background. As a result, when a user presses "Back" from one of these screens, they return to find the drawer still covering the home screen instead of seeing the main content.

Steps to reproduce
  1. Click on drawer icon
  2. Click on Profile, Reports, or Settings
  3. Navigate back and you can see the issue
What was the expected result?

The navigation drawer should close automatically when a menu item is tapped. When navigating back to the home screen, the drawer should be closed rather than remaining open on top of the content.

Put here any screenshots or videos (optional)

https://github.com/user-attachments/assets/ff0243b7-73ea-4e99-bde3-efd92407434e

How can we contact you (optional)

Github | Linkedin | chetanr25.in

Would you like to work on this issue?

Yes

By submitting this issue, I have confirmed that:
  • I have starred the repo ⭐ and watched 👀 it on GitHub and followed the contribution guidelines.
Dominant language
Dart
Stars
244
Forks
179
Avg merge
12h 42m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CCExtractor/taskwarrior-flutter

All issues in CCExtractor/taskwarrior-flutter

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.