Skip to content

Add horizontal padding to the Pagination container#490

Merged
NotYuSheng merged 1 commit into
mainfrom
fix/pagination-container-padding
Jul 8, 2026
Merged

Add horizontal padding to the Pagination container#490
NotYuSheng merged 1 commit into
mainfrom
fix/pagination-container-padding

Conversation

@NotYuSheng

Copy link
Copy Markdown
Owner

Bug (user-reported)

On the monitor Subnets panel, the pager's "Showing X of Y" text and the nav controls were flush against the left/right edges of the component with no gap.

Cause

The shared .pagination-container had padding: 1rem 0vertical padding only. Pagers that are dropped directly into a bordered container (the #477 batch: SubnetsPanel, ExternalEventsPanel, BaselineDefinitionPanel, etc.) had no horizontal breathing room. It only looked fine on ExtractedFiles/FileList because those were wrapped in a padded <div>.

Fix

padding: 1rem 0padding: 0.75rem 1rem on .pagination-container, so every pager gets horizontal padding regardless of placement. One-line CSS change; affects all pagers uniformly.

Verification

Playwright: the extracted-files pager now reports padding-left/right: 16px (was 0); screenshot confirms the info + nav sit with even gaps from the edges. Same component backs the Subnets pager, so it's fixed by the same change.

🤖 Generated with Claude Code

The shared .pagination-container had `padding: 1rem 0` (vertical only), so when
a pager is dropped directly into a bordered container — e.g. the monitor Subnets
panel — the "Showing X of Y" text and the nav hugged the left/right edges with no
gap. Add 1rem horizontal padding so every pager has breathing room regardless of
where it's placed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@NotYuSheng, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 398d83ae-3ba3-4ce6-b195-15c40682cd4b

📥 Commits

Reviewing files that changed from the base of the PR and between 1e0b034 and f000d8e.

📒 Files selected for processing (1)
  • frontend/src/components/common/Pagination/Pagination.css

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the padding of the Pagination component in Pagination.css from 1rem 0 to 0.75rem 1rem to prevent elements from hugging the edges when placed inside bordered containers. A comment explaining this layout adjustment has also been added. There are no review comments, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@NotYuSheng NotYuSheng merged commit 787c11f into main Jul 8, 2026
3 checks passed
@NotYuSheng NotYuSheng deleted the fix/pagination-container-padding branch July 8, 2026 03:42
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.

1 participant