Skip to content

refactor(ui): centralize product icon-button padding in EMCN - #7987

Merged
waleedlatif1 merged 1 commit into
stagingfrom
codex/control-fix-padded-icon-buttons
Sep 18, 2026
Merged

waleedlatif1 merged 1 commit into
stagingfrom
codex/control-fix-padded-icon-buttons

Conversation

@BillLeoutsakosvl346

Copy link
Copy Markdown
Contributor

Summary

Product icon actions repeatedly force p-1! or p-1.5! over EMCN Button's text-button padding. Add optional iconPadding='sm' | 'md' variants to the existing Button and migrate all 57 product occurrences across 19 consumer files. For example, a terminal copy button now uses iconPadding='md' while keeping its -m-1.5 layout margin.

The selected padding is composed after size and resolved by the existing class merger, so it needs no !important. Existing sizes, colors, corner radii, icon strokes, labels, handlers and disabled states are preserved. Button defaults are unchanged. Remove the unused terminal ROW_STYLES.iconButton recipe as well.

Landing pages are excluded. This PR contains only 21 product files; all audit scripts, reports and browser fixtures remain outside the branch. No new dependencies or tests.

Testing

  • 343 existing EMCN tests and 46 relevant app tests passed; EMCN/app type checks, repository lint and API validation passed.
  • AST comparison verifies all 57 consumer changes are limited to moving padding into the new prop; children, event handlers and other props remain identical.
  • External Chromium fixtures use real before/after Button renders and compiled app CSS: 354 comparisons match across light/dark idle, disabled and hover states. All 70 existing variant/size combinations without the new prop render identical markup. These are isolated component comparisons, not end-to-end product navigation.
  • Final external category audit: 57 findings → 0; broader findings 1060 → 1003, with the other findings unchanged. Product source search finds no remaining old padding recipes. Landing diff is empty.
  • Committed-diff conformance audit: zero usage violations; two expected central-definition notices for the new padding options. The full inventory still has unrelated findings and analysis gaps.

@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Sep 18, 2026 10:13pm UTC

Request Review

@greptile-apps

greptile-apps Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

The PR appears safe to merge; the centralized variants preserve the migrated padding behavior without changing Button defaults or consumer interactions.

Summary

This PR centralizes content-sized icon-button padding in the EMCN Button component and migrates product consumers away from local important padding utilities.

  • Adds sm and md iconPadding variants without changing the default Button behavior.
  • Replaces local p-1! and p-1.5! overrides while preserving unrelated layout classes such as fixed dimensions and negative margins.
  • Removes the terminal’s now-unused icon-button style recipe.

Reviews (1) · Last reviewed commit: "refactor(emcn): centralize product icon-..."

@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 21 files

Confidence score: 5/5

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

Re-trigger cubic

@waleedlatif1
waleedlatif1 merged commit 0b7c6ae into staging Sep 18, 2026
37 checks passed
@waleedlatif1
waleedlatif1 deleted the codex/control-fix-padded-icon-buttons branch September 18, 2026 22:27

This branch was successfully deployed

1 active deployment
Preview 9de79988 Deployed Sep 18, 2026 by vercel[bot]
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