Margaret-Petersen / Margaret-Petersen/flower-ordering-app-with-source-code
Loader Keeps Spinning on Tab After Adding a Category – Admin Panel
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Product page in the admin panel and reproduce category creation in Chrome on Windows 11. Trace the loader around the category creation API call; done means the category is added and the tab or section-header loader disappears after the action completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100