Repository navigation
fix: keep request cards readable across themes and narrow layouts - #6
Merged
Merged
Conversation
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.
Approval and question cards use fixed light backgrounds and low-contrast labels that become difficult to read in dark mode. Use the existing theme text and panel colors for cards, details, and form controls, with visible focus and selected states.
Wrap long content and action buttons within narrow cards, and use the existing spacing and radius tokens. Lower the styling-audit baseline to reflect the removed raw colors.
Validation
VITEST_MAX_WORKERS=4 npm run check: 1,038 tests passed, 2 skipped; styling audit, TypeScript, and production build passed.Screenshots
Synthetic browser fixtures at 360 px, with long content to exercise wrapping: