lambertf917 / lambertf917/cafe-ordering-system-using-react-js

Search Results Displayed at the Bottom of the Page on Enatega Website, Making It Difficult for Users to Confirm Search Functionality

Open
#180 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
On the Enatega website, search results are displayed at the bottom of the page, making it difficult for users to quickly verify if their search has worked. Users must scroll down to see the results, which could lead to confusion and frustration, especially if the search results are not immediately visible.

To Reproduce

Open the Enatega website.
Type a search term (e.g., a restaurant name, dish, or type of food) in the search bar.
Hit "Search" or press enter.
Observe that the search results are placed at the bottom of the page, and users must scroll down to see them.
Expected behavior
Search results should be displayed near the top of the page, or in a clear and visible section immediately following the search, so users can easily confirm if their search has worked.

Actual Behavior:
Search results are placed at the bottom of the page, requiring users to scroll down to find the results, making it unclear whether the search function has worked properly.

Desktop (please complete the following information):

OS: Windows
Browser: Chrome

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 tracing the website search bar and the rendering path for search results in the frontend. Reproduce the issue in Chrome with a restaurant, dish, or food-type query, then verify that results appear near the top or in a clearly visible section immediately after searching.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend, search
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.