KROMA SYSTEM / 01ENGINEERING DIGITAL GROWTH

BOOT_SEQUENCE // KROMACODE.TECH

Mapping the system000
CREATIVE SYSTEMSWEB / AI / GROWTHREADY WHEN YOU ARE
KC
KROMA CODE
// kromacode.tech
// ROUTE_TRANSITION_SYS :: BLOG/FIGMA COMPONENT VARIANTS PROPERTY BUGS/
STATUS: 200 OK
LIVE DEV GAG / REALITY CHECK:

"Yash reviewing pull requests at 3:14 AM again..."

COMPILING UI NODES0%
// KROMA CODE BLOG :: FIGMA & DESIGN SYSTEMS

Solving Figma Component Variant Bugs: State Mutations, Overrides, and Nesting Glitches

Yash Kumar Singhβ€’ 11 min readβ€’July 25, 2026
πŸ’‘ ARTICLE EXECUTIVE SUMMARY: "Why do custom button labels reset when switching variants from Hover to Active? Learn the gold standard for structuring component variant sets in enterprise Figma libraries."

1. The Infuriating Text Override Reset Bug

You carefully type a custom button label (e.g. "Transmit Inquiry"), but as soon as you toggle the variant property to State=Hover or Icon=True, the text instantly resets back to "Default Button". This occurs because layer names inside variant frames do not match 100% identically across variants.

2. The Layer Name Alignment Rule

For Figma to preserve text overrides and icon swaps when toggling component variants, **every single sub-layer inside every variant variant must share the exact same layer name and node hierarchy structure**.

  • ❌ Variant 1: Frame 12 > text_node | Variant 2: Group 4 > label (Text resets)
  • βœ… Variant 1: Button_Content > Label_Text | Variant 2: Button_Content > Label_Text (Overrides preserved!)

3. Component Property Best Practices

Utilize Boolean Properties for toggling icons, Text Properties for string inputs, and Instance Swap Properties for icon selections instead of creating thousands of redundant variant combinations.

// INTERCONNECTED TOPICAL LINKS
Written by Yash Kumar Singh (Founding Engineer at Kroma Code, Lucknow)
Consult With Author