Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Search Interface: Lack of Spacing Between Input and Button in Mobile View #303

Closed
1 task
SisiVero opened this issue Oct 18, 2024 · 0 comments · Fixed by #307
Closed
1 task

[Bug] Search Interface: Lack of Spacing Between Input and Button in Mobile View #303

SisiVero opened this issue Oct 18, 2024 · 0 comments · Fixed by #307
Assignees
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@SisiVero
Copy link
Contributor

Description

In the mobile view, the search input and search button are displayed in a column layout. However, there is no space between the two elements, causing them to cluster together, which affects usability. This issue does not occur on desktop screens, where the elements are displayed side by side without spacing issues.

Reproduction

  1. Open the search interface on a mobile device or use developer tools to simulate a mobile screen size.
  2. Observe the search input and search button in the column display.
  3. Note the lack of space between the elements.
  4. See error.

Expectation

There should be adequate space between the search input and the search button in mobile view to avoid clustering and improve the user experience (UX).

Screenshots

Without spacing:
noGap
with space:
gapApplied

Resolution

  • I would be interested in resolving this bug.
@SisiVero SisiVero added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Oct 18, 2024
@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work and removed 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Done
2 participants