Repository navigation
fix(ui): unify Tailwind styles and mobile inputs - #25
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.
Touching the filename or extension input on iOS could zoom the page, and the placeholders used a different font stack from the rest of the UI. Touch inputs now use 16px text, mobile text fields share an 8px radius, and Send occupies a full row below 640px. History code snippets also gain 4px of space above their container.
The SPA and shared public components now use Tailwind v4 theme tokens and native utilities for fonts, layout, sizes, and interaction states. Global CSS uses base/component layers, with custom utilities for continuous corners and scrollbars. The suffix picker keeps its coordinated close transition and correctly honors reduced motion while open. DEVELOPMENT.md documents the styling conventions, and the public-page test checks the accessible logo link instead of a removed CSS class.
The viewport zoom limits are included, although iOS Safari may ignore them. Broad style changes can affect browser-specific rendering; Chromium checks covered widths from 320px to 1280px, five locale font stacks, dropdown open/search/select/close, mode switching, and card creation/editing/deletion. iPhone Safari was not directly automated.
Validation:
mise run test: quality gate, production builds, favicon tests, and all 40 Vitest tests passed.git diff --check: passed.