Skip to main content
Question

Prototype mode interactions not working with keyboards arrows left or right correctly

  • August 5, 2026
  • 3 replies
  • 10 views
Lenin

Hi Figma support,

We are having a issue with in prototype mode for specific flow when navigating with keyboard arrow left and right voor next or previous frame in the flow.

 

  • Description of the bug/issue
    • When navigation through a prototype with your arrow keys left or right. The prototype stays stuck and is only able to navigate to the first 2 frames and doesn’t further through the whole prototype.
       
  • Reproduction path (Simple)
    • Create 4 frames with previous en next buttons
    • Link the next buttons to the next frame and previous frame
    • Start prototype mode
    • Click on the buttons you can go through the flow (works fine)
    • Use keyboard keys left and right to go through the prototype (doesn’t work correctly)
    • It gets stuck on the first and 2nd frame when navigating which keyboard arrows
  • Figma in Chrome and Figma app
  • Tahoe 26.6 , Chrome browser 150.0.7871.187 ,  Figma app 126.7.10

 

  • Trouble shooting we’ve done
    • Relink all the frames
    • Create a brand new file move the frame and relink
    • Cut and Paste within the same file or other file
    • Removing frames and connecting to different frames.

3 replies

djv
Figmate
  • djv
  • Community Support
  • August 5, 2026

Hi ​@Lenin, thanks for reaching out! 

I understand how this must be affecting your workflow. The "stuck looping on the first two frames" pattern is one we've seen before, and it usually traces back to how Figma calculates frame order for keyboard navigation (it's separate from the click-based interactions, which is why your buttons still work fine). A couple of quick things that'll help us pin it down:

  1. Are you using any Flow Starting Points in this file? Those intentionally limit keyboard nav to just that flow.
  2. How are the 4 frames physically arranged on the canvas (left-to-right, stacked, etc.)? Keyboard order follows canvas position, and adding/editing interactions can sometimes shift that order unexpectedly.
  3. Does the same loop happen in a fresh test file with no interactions at all, just using 4 plain frames?

In the meantime, a temporary solution that should get you moving again: add explicit Key/Gamepad interactions to each frame (left arrow → previous frame, right arrow → next frame) directly, rather than relying on the automatic canvas-order navigation. It's a bit more manual, but it sidesteps the ordering issue entirely. Let us know these details and we can continue troubleshooting with you, as needed. 

Lenin
  • Lenin
  • Author
  • New Member
  • August 7, 2026

Hi ​@djv ,

Thank you for answering. And for providing a temporary solution.

Yes the flow has a starting point. The frames are horizontal left-to-right. And i reproduced it in a new file with basic frame and rectangle as a button for purpose of testing, to make sure i wasn’t the file it self.

Also i forgot to mention that the controls you get in the center in prototype mode those have the same issue as keyboard.

adamsmasher
Figmate
  • adamsmasher
  • Figmate
  • August 9, 2026

Hi, ​@Lenin - stepping in for ​@djv. Thanks for doing some additional troubleshooting - sounds pretty confusing for you!

 

With your new file, did you include any interactions? It sounds like you might have since you mentioned including a button to test with. Can you try one more time by adding several frames to the canvas in a left-to-right order, but include no interactions and then test the prototype? Once we’ve verified that this is working as expected, you can try adding an interaction to see how that affects the prototype.

Terms & ConditionsAccessibility statement