OWASP/Nest

inconsistent bottom spacing below search component across pages on mobile

Open

#5,148 opened on Jul 7, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (651 forks)auto 404
buggood first issue

Repository metrics

Stars
 (412 stars)
PR merge metrics
 (Avg merge 2d 12h) (128 merged PRs in 30d)

Description

Community & Support: LinkedIn Group · Slack #project-nest

Active project leaders: Arkadii Yakovets -- GitHub · LinkedIn · Slack; Kate Golovanova -- GitHub · LinkedIn · Slack

Contributing · Code of Conduct · GSoC Mentors

Describe the bug The spacing below the Search component is inconsistent across different Nest pages in mobile viewport. Some pages include adequate vertical spacing between the search bar and the content below it, while others have little to no spacing, resulting in an inconsistent visual layout.

To Reproduce Steps to reproduce the behavior:

  1. Resize to mobile viewport
  2. Navigate to the Projects/Members page, and observe that there is no vertical spacing below the Search bar
  3. Now nevigate to the Chapters/Committees page and ovserve the presence of vertical spacing

Expected behavior The Search component should have consistent bottom spacing across all pages where it is used, ensuring a uniform layout and visual hierarchy.

Are you going to work on fixing this?

  • Yes
  • No

Screenshots Plenty of vertical spacing / margin below search bar

No vertical spacing below the search bar

Desktop (please complete the following information):

  • OS: Linux
  • Browser: Zen/Firefox

Contributor guide

Research direction
Investigate how the Search component is used on the Projects, Members, Chapters, and Committees pages. Compare the CSS margins/spacing below the search bar and identify why it differs. Standardize the bottom spacing for consistent mobile layout.
Tech stack
csshtml
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBasic CSS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85