OWASP / OWASP/OpenCRE

Mobile Navbar Lacks Close Functionality In Full-Screen

Open
#646 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
180
Forks
137
Avg merge
3d 23h
Merged PRs (30d)
21

Description

Image

On mobile devices, after clicking the navigation bar (hamburger) icon, the navbar opens and occupies the entire screen space.

This design presents two critical usability issues for users trying to close the navigation menu:

  • Missing Close Button: There is no dedicated "X" or "Close" icon within the full-screen navbar.
  • No Outside Click Area: Because the navbar covers the full screen, the user cannot click outside of the menu area to close it.

Current User Experience (UX): Once the navbar is open, the only way to close it and return to the main content is typically by using the browser's "Back" function or refreshing the page, which is not intuitive and disrupts the user's flow.

Expected Behavior: The mobile navbar should be easily dismissible. This could be achieved by:

  • Adding a visible "Close" icon (e.g., an "X" or a back arrow) to the top of the full-screen navbar.
  • Allow a portion of the main content to remain visible so that clicking outside the menu area can close it.

@robvanderveer / @northdpole
Assign this issue to me and share your thoughts on this issue.

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.

Research direction

Start by locating the mobile navbar implementation and reproduce the full-screen menu behavior on a mobile viewport. Confirm the menu can be dismissed without browser navigation, using either a visible close control or an outside-click area, and verify the main content remains usable.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.