Loader Keeps Spinning on Tab After Adding a Category – Admin Panel

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by reproducing the issue on the Product page in the admin panel using Chrome, then trace the category creation flow and its loader state around the category creation API call. Done means the category is added successfully and the tab or header loader stops, showing a completed action.

Written by the indexing model from the issue text.

Description

Describe the bug
When adding a new category from the Product page in the admin panel, a loader appears on the tab (likely the browser tab or section header) and continues spinning indefinitely, even after the category has been successfully added. This suggests that the action is incomplete or stuck, although the category may have been added in the background.

To Reproduce
Steps to reproduce the behavior:

Open the Product page in the admin panel

Use the dropdown to add a new category

Observe the tab or header loader animation

Notice that the loader does not stop, even after the action is done

Expected behavior
The loader should disappear once the category is successfully added and the action is complete, indicating to the user that the process is finished.

Screenshots

Recording 2025-06-24 120712.zip

Desktop (please complete the following information):

OS: Windows 11

Browser: Chrome

Version: 123.0.6312.86

Additional context
This may be caused by a missing or delayed response handler after the category creation API call. It can mislead users into thinking the process is still running or has failed. A proper success state and loader dismissal should be implemented.

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

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.

More from raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.