Mobile: Sidebar drawer leaves bottom gap when scrolling
- Dominant language
- Python
- Stars
- 451
- Forks
- 707
- Avg merge
- 22h 59m
- Merged PRs (30d)
- 91
Description
Community & Support: [LinkedIn Group](https://www.linkedin.com/groups/14656108/) · [Slack #project-nest](https://owasp.slack.com/archives/project-nest)
Active project leaders: Arkadii Yakovets -- [GitHub](https://github.com/arkid15r/) · [LinkedIn](https://www.linkedin.com/in/arkid15r/) · [Slack](https://owasp.slack.com/team/U060W3NKLTF); Kate Golovanova -- [GitHub](https://github.com/kasya/) · [LinkedIn](https://www.linkedin.com/in/kate-golovanova/) · [Slack](https://owasp.slack.com/team/U07PWB1JZ6Z)
[Contributing](https://github.com/owasp/nest/blob/main/CONTRIBUTING.md) · [Code of Conduct](https://github.com/owasp/nest/blob/main/CODE_OF_CONDUCT.md) · [GSoC Mentors](https://github.com/owasp/nest/blob/main/MENTORS.md)
---
**Describe the bug**
On mobile devices, the sidebar drawer does not fully cover the viewport height. When scrolling, a visible gap appears at the bottom of the screen, exposing background content.
---
**To Reproduce**
Steps to reproduce the behavior:
1. Open the application on a mobile device
2. Open the sidebar menu
3. Scroll the page
4. Observe a gap appearing at the bottom of the sidebar
---
**Expected behavior**
The sidebar should fully cover the viewport height and remain consistent during scrolling, without leaving any visible gaps.
---
**Are you going to work on fixing this?**
* [x] Yes
* [ ] No
---
**Screenshots**
Attach screenshots and/or screen recording demonstrating the issue.
https://github.com/user-attachments/assets/a66ab2d7-7b28-4da7-8cab-1c51ebce5f32
---
**Desktop (please complete the following information):**
* Not applicable (issue is mobile-specific)
---
**Smartphone (please complete the following information):**
* Device: Samsung Galaxy S24 FE
* OS: Android
* Browser: Chrome
* Version: (optional)
---
**Additional context**
This issue seems related to how viewport height is handled on mobile devices, as it only occurs on mobile and not on desktop. Further investigation may be needed to identify the exact cause.
Contributor guide
Assessment
This issue has not been assessed yet.