[NO-TICKET] Use min-width in Table and Pagination for responsive breakpoint consistency #3482
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.
Summary
The HCgov Accounts team recently worked on a feature that implemented stackable Table components. During visual QA, we noticed that the table layout would change at one pixel wider than the rest of the other responsive components on the page. During debugging, I noticed that
_Table.scsswas specifying breakpoints with@media (max-width: $media-width-X) { ... }while the rest of the DS components usedmin-width: $media-width-X(<Pagination>also usesmax-widthin one spot).This PR updates the media query breakpoint rules in the
<Table>and<Pagination>components to usemin-widthrather thanmax-widthto set the breakpoints.How to test
<Alert>and<Table>components re-flow together at the same widths.Checklist
[WNMGDS-####] Titleor [NO-TICKET] if this is unticketed work.Type(only one) label for this PR, if it is a breaking change, label should only beType: BreakingImpacts, multiple can be selected.If this is a change to design:
If this is a change to code:
npm run test:unitandnpm run test:browser:allwere each successfulnpm run test:unit:update) and browser-test snapshots (npm run test:browser:all:update)If this is a change to documentation: