Repository navigation
fix: keep supported device table headings readable (DEVDB-482) - #762
Merged
Merged
Conversation
This branch was successfully deployed
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.
The production docs review exposed the Supported heading breaking onto two lines inside provider panels. Reserve enough width for that column and keep table headings on one line. At the narrowest panel widths, adjust heading size and column proportions so labels fit without overlap.
Compact hardware facts preserve the minimum width of words while allowing color swatches to wrap. The approved checks renderer and requirement data are unchanged.
Validation: Prettier, Stylelint, and CSS build passed. Chromium geometry checks passed for August, Nuki, KeyInCode, and Salto at desktop, 390px, and 320px widths: all three headers stay on one line, stay within provider panels, do not overlap, and the component has no horizontal overflow. CSS-only follow-up to #761.
Docs patch: https://github.com/seamapi/docs/pull/1572
https://linear.app/seam/issue/DEVDB-482