Skip to content

feat(loading-skeleton): responsive sizing across mobile/tablet/desktop - #349

Open
otsimaofficial wants to merge 1 commit into
Goldii-locks:mainfrom
otsimaofficial:feat/loading-skeleton-responsive-275
Open

feat(loading-skeleton): responsive sizing across mobile/tablet/desktop#349
otsimaofficial wants to merge 1 commit into
Goldii-locks:mainfrom
otsimaofficial:feat/loading-skeleton-responsive-275

Conversation

@otsimaofficial

Copy link
Copy Markdown

Problem & Goal

LoadingSkeleton used a fixed 1→3 column grid and static padding, so it didn't scale cleanly between mobile, tablet, and desktop viewports.

Changes

  • Stat grid now stacks grid-cols-1 on mobile → sm:grid-cols-2 on tablet → md:grid-cols-3 on desktop.
  • Header and content rows use responsive padding/spacing (p-4 sm:p-6, space-y-4 sm:space-y-6) and the header stacks flex-colsm:flex-row.
  • Placeholder bar widths switch from a fixed width to w-full sm:w-* so they don't overflow narrow screens.
  • Added data-testids (loading-skeleton, loading-skeleton-card, loading-skeleton-stats, loading-skeleton-rows) for test targeting.

Testing

  • New __tests__/loading-skeleton-responsive.test.tsx (9 tests) asserts the responsive class breakpoints and that the accessible loading announcement is preserved.
  • npx tsc --noEmit, the new test file, and npm run build all pass locally.

Note: npm run lint currently fails on this repo's main due to a pre-existing, unrelated react-hooks/set-state-in-effect error in SignatureTimeoutAlert.tsx (visible on the last several merged PRs' CI runs). That's fixed independently in a separate PR and isn't touched here.

Closes #275

🤖 Generated with Claude Code

Stack the stat grid and content rows to a single column on mobile,
two on tablet, three on desktop, and use responsive padding/spacing
so LoadingSkeleton scales cleanly at every breakpoint.

Closes Goldii-locks#275
@drips-wave

drips-wave Bot commented Aug 29, 2026

Copy link
Copy Markdown

@otsimaofficial Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement responsive sizing layouts on loading_spinner_skeleton

1 participant