OWASP / OWASP/Nest

[BUG]: Loading skeleton count does not match page size on Users and Organizations pages

Open
#4,267 3 comments 0 reactions 0 assignees View on GitHub
bug enhancement
Dominant language
Python
Stars
451
Forks
707
Avg merge
22h 59m
Merged PRs (30d)
91

Description

**Describe the bug**
On the Users and Organizations listing pages, the loading skeleton displays 12 placeholder cards while the page actually fetches 24 items per page.
When the data loads, the grid expands from 12 skeleton cards to 24 real cards, causing a visible layout shift.
This creates a small UI inconsistency during the loading state.

**To Reproduce**
1. Go to /members or /organizations
2. Enable network throttling in browser DevTools (Slow 3G)
3. Refresh the page
4. Observe that only 12 skeleton cards are displayed
5. After data loads, the grid expands to 24 cards

**Expected behavior**
The number of skeleton placeholders should match the expected page size (24 items) to prevent layout shift and maintain a consistent loading UI.

**Are you going to work on fixing this?**

- [x] Yes
- [ ] No

**Desktop (please complete the following information):**
- OS: Windows 11
- Browser: Chrome
- Version: 122+

**Smartphone (please complete the following information):**

- Device: N/A
- OS: N/A
- Browser: N/A
- Version: N/A

**Additional context**
This appears to be caused by the skeleton component rendering 12 placeholders while the listing pages request 24 items.
Aligning the skeleton count with the page size (24) or making it configurable could prevent layout shifts during loading.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.