Skip to main content
Question

Why does the prototype break my existing component states?

  • August 4, 2026
  • 1 reply
  • 7 views
Becky Black

I’m building a prototype using existing components which have hover states, focus states and key pad navigation. I can set the component up and it works perfectly with keyboard navigation, however as soon as it’s in the prototype the keyboard commands stops working.

I’m having the same problem with the slots  independently they work but as soon as I put them in the slot they stop working. Does anyone know why it’s doing this?

1 reply

Jaycee Lewis
Figmate

Hey hey ​@Becky Black 👋 

To help track down what's happening, could you share a short screen recording of the prototype in Present mode? Ideally it shows you clicking into the flow, then attempting the keyboard interaction that isn't registering. That'll show us more and help give you the best answer. — Jaycee

A couple other things worth checking:

  • When you try Tab or Arrow keys in the prototype, does anything visually change (focus ring, outline, state shift) — or is there no response at all?
  • For Slots specifically — one thing worth checking is whether the interactive component still responds to keyboard nav when it's a fresh instance dropped directly on the canvas (not nested in a slot), just to isolate whether the slot itself is the variable

Thanks for the additional information! — Jaycee

Terms & ConditionsAccessibility statement