Skip to content

[SPARK-55810][UI] Fix missing spacing between table and pagination controls in Jobs and Stages page#55626

Open
XdithyX wants to merge 1 commit intoapache:masterfrom
XdithyX:master
Open

[SPARK-55810][UI] Fix missing spacing between table and pagination controls in Jobs and Stages page#55626
XdithyX wants to merge 1 commit intoapache:masterfrom
XdithyX:master

Conversation

@XdithyX
Copy link
Copy Markdown

@XdithyX XdithyX commented Apr 30, 2026

What changes were proposed in this pull request?

This PR fixes a UI regression in the Spark Web UI (Jobs and Stages pages) where spacing between the data table and the pagination controls ("Page", "Jump to", "Show items") was missing (SPARK-55810).

The issue was introduced during the Bootstrap upgrade in #54552, which caused the pagination controls to appear visually attached to the table. This change restores appropriate spacing between these elements to improve layout clarity and consistency.

Why are the changes needed?

Without proper spacing, the table and pagination controls appear cramped and visually misaligned, which negatively impacts readability and overall user experience in the Spark Web UI.

This is a regression caused by the Bootstrap upgrade and should be fixed to maintain UI consistency.

Does this PR introduce any user-facing change?

Yes.

It improves the visual layout of the Jobs and Stages pages in the Spark Web UI by restoring proper spacing between the table and pagination controls.

How was this patch tested?

  1. Built Spark locally and ran spark-shell
  2. Opened the Spark Web UI and navigated to the "Jobs" and "Stages" tabs
  3. Verified that spacing between the table and pagination controls is correctly applied
  4. Compared behavior before and after the fix to confirm the issue is resolved

Was this patch authored or co-authored using generative AI tooling?

No.

Screenshots

Stages page before the fix Stages page after the fix
Screenshot 2026-04-30 at 9 16 55 PM Screenshot 2026-05-01 at 9 28 42 PM
Jobs page after the fix
Screenshot 2026-05-01 at 9 28 26 PM
Screenshot 2026-05-01 at 10 37 43 PM

@XdithyX
Copy link
Copy Markdown
Author

XdithyX commented Apr 30, 2026

@dongjoon-hyun @yaooqinn Can you please take a look? Thanks!

@sarutak
Copy link
Copy Markdown
Member

sarutak commented May 1, 2026

Hi @XdithyX, could you enable GA in your forked repository?
Also, could you put screenshots for Jobs page too?


<div class="d-flex justify-content-between align-items-center">
<div class="d-flex align-items-center">
<div class="d-flex align-items-center mb-3">
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Adding mb-3 only to the left inner child breaks symmetry inside the flex container. The left child gains a 1rem bottom margin, but the right child (the Jump-to form) does not, so the two children's bottom edges no longer align under align-items-center. Also, since pageNavigation() is rendered both above and below the table, the same mb-3 gets applied to the bottom nav as well, adding unnecessary spacing there.

Suggested fix: apply the margin to the outer flex container instead:

-    <div class="d-flex justify-content-between align-items-center">
-      <div class="d-flex align-items-center mb-3">
+    <div class="d-flex justify-content-between align-items-center mb-3">
+      <div class="d-flex align-items-center">
         <span class="pe-1">Page: </span>
         <ul class="pagination mb-0">

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@sarutak Thanks for pointing this out! You're right, the margin should be applied to the outer flex container to keep alignment consistent.
I’ve updated the change accordingly. The earlier version mistakenly applied mb-3 to the inner container.
Also, I have enabled github actions on my fork, CI is currently running.
Added screenshots for Jobs page as well.

Thanks!

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.

2 participants