MudDataGridPager: Fix page-size select absorbing toolbar space - #13583
Merged
danielchalmers merged 2 commits intoAug 7, 2026
Merged
Conversation
MudBlazor#13573 changed .mud-table-pagination-spacer from `flex: 1 1 100%` to `flex: 1 1 auto`. The 100% basis had over-subscribed the flex line, so flex-grow never ran on any toolbar child. With an auto basis there is positive free space for the first time, and .mud-select carries flex-grow: 1, so the page-size select soaks it up. MudDataGridPager renders the select as a direct child of the toolbar, so it is affected; MudTablePager nests it in a wrapper div, so it is not. Measured at a 1400px container, the select grew from 88px to 532px. Setting flex-grow: 0 on the direct child restores the pre-MudBlazor#13573 geometry exactly while keeping the wrap behaviour MudBlazor#13573 added.
Member
Author
2 tasks
danielchalmers
deleted the
claude/datagridpager-spacing-regression-a41e4f
branch
August 7, 2026 13:43
This was referenced Aug 24, 2026
This was referenced Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Fixes #13580 — a v9.8.0 regression from #13573.
What happened
#13573 changed
.mud-table-pagination-spacerfromflex: 1 1 100%toflex: 1 1 auto. The100%basis had over-subscribed the flex line, soflex-grownever ran on any toolbar child. With anautobasis there is positive free space on the line for the first time — and.mud-selectcarriesflex-grow: 1(_select.scss:3). The spacer and the select then split the slack and the select balloons.MudDataGridPagerrenders<MudSelect>as a direct child of the toolbar, so it is affected.MudTablePagernests it in<div class="@PaginationClassname">, so it is not — which is exactly what the reporter noticed.The change
One rule, scoped to direct children so
MudTablePagercannot be reached:flex-grow: 0rather thanflex: 0 0 auto: both measure byte-identical across every scenario below, including a 200px container, because the select is never the shrink target. The narrower statement leaves shrink alone.Verification
Real compiled stylesheets from the
v9.7.0tag, thev9.8.0tag, andv9.8.0+ this change, applied to pager DOM captured fromdev.mudblazor.com, measured over CDP at--force-device-scale-factor=1.Rows-per-page select outer width:
Toolbar height, nav-button inset from the end edge, and overflow are identical to v9.7.0 in every LTR and RTL case.
#13573's benefit is preserved. At a 320px container on a 700px viewport (narrow container, wide viewport — the
max-width: 416pxrule does not fire):Not addressed here
Both are pre-existing in v9.8.0 and unchanged by this PR:
Separately,
.mud-select { flex-grow: 1 }applies to anyMudSelectplaced directly in a flex container, so this failure mode can recur wherever a flex parent gains free space.Checklist: