Skip to content

feat(design-system): reduce default form-control height to 32px#6699

Merged
macko911 merged 4 commits into
masterfrom
matej/nan-6160-reduce-default-form-control-height-to-32px
Jul 7, 2026
Merged

feat(design-system): reduce default form-control height to 32px#6699
macko911 merged 4 commits into
masterfrom
matej/nan-6160-reduce-default-form-control-height-to-32px

Conversation

@macko911

@macko911 macko911 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Problem

Inputs and the buttons/controls beside them rendered at 36px with a 4px corner radius, reading heavier and rounder than the rest of the redesigned UI. Inputs and inline buttons only stayed aligned because both were pinned to 36px.

Solution

  • Drop the design-system Input/InputGroup/Textarea and the webapp Select trigger and ScopesInput to a 32px control height.
  • Move buttons that sit inline with an input or in a header/toolbar/form row from lg to md: the DS component triggers (Combobox, MultiSelect, FilterMultiSelect, PeriodSelector, IntegrationDropdown), the AuthCredentials refresh buttons, and content-page actions across integrations, connections, function detail, and team settings. Shrink LineSnippet to match the adjacent "View code" button.
  • Reduce the input radius from 4px (rounded-ds-sm) to 2px (rounded-ds-xs) on Input/InputGroup/Textarea and the Select trigger, matching the button radius.
  • Keep the lg button size for prominent CTAs and full-width form submits (auth pages, Getting Started, empty-state create buttons, dialog actions), which stay intentionally larger.

Fixes NAN-6160

Testing

  • Verified live on dev: inputs and their adjacent buttons/controls render at 32px and aligned across Logs, environment settings, connection auth, integrations, functions, and team settings; kept-lg CTAs still measure 36px.

Inputs and their inline buttons rendered at 36px, reading heavier
than the rest of the redesigned UI. Drop the Input/InputGroup default
to 32px (h-8) and match the webapp Select trigger and ScopesInput
chips container.

Buttons that sit inline with an input move from lg to md (Combobox,
MultiSelect, FilterMultiSelect, PeriodSelector and IntegrationDropdown
triggers, the KeyValueInput remove button, and the AuthCredentials
refresh buttons). The lg size is kept for prominent CTAs and full-width
form submits, which stay intentionally larger.
@linear-code

linear-code Bot commented Jul 6, 2026

Copy link
Copy Markdown

NAN-6160

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Preview Deploy

Status URL Deploy Logs Last Updated
✅ Ready Preview URL Deploy Logs 7 Jul 2026, 15:13 UTC

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 15 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Re-trigger cubic

Extend the 32px control height to lg buttons on content pages that sit
in a header, toolbar, or form row next to inputs: the integrations list
and detail headers, the functions filter toolbar and View code button,
connection list/create/settings actions, and team settings. Shrink the
LineSnippet command box to match the adjacent View code button.

The lg size stays for auth submit buttons, Getting Started onboarding,
centered empty-state CTAs, and dialog footer actions.
@macko911
macko911 marked this pull request as ready for review July 7, 2026 09:51
Input, InputGroup and Textarea used radius/sm (4px). Move them to
radius/xs (2px) to match the button radius.
Match the Select trigger radius to the 2px input radius.
@macko911
macko911 added this pull request to the merge queue Jul 7, 2026
Merged via the queue into master with commit e498f45 Jul 7, 2026
35 checks passed
@macko911
macko911 deleted the matej/nan-6160-reduce-default-form-control-height-to-32px branch July 7, 2026 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants