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

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. 

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.

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.

Hi ​@adamsmasher , 

I’ve made another file to walk through your suggestion.

By putting all the frames from left-to-right with out interactions the keyboard arrows work. After adding interaction to the buttons (simple rectangles low effort for testing purpose). The behaviour i’ve described before starts occuring again.

So it seems that interaction and keyboard arrows don’t work like they used to work before.

Ok, that makes some sense since the arrows will follow the interaction flow. Having said that, you’re finding that it’s not following the interaction flow the way you’d expect, right? You’ve got a couple options still to get what you want:

1. Set up explicit key press interactions: Add "On KeyPress (Left/Right Arrow) → Navigate To" interactions to each frame (as ​@djv advised in a previous reply).
2. Delete all prototype starting points: This makes the viewer treat the prototype as a slideshow (respecting sequential arrow key navigation) while still allowing interactions to function. Note: this also means you can no longer limit which frames are shared with viewers.

Thank you for these options

Beside a new behaviour it’s going to be some extra work to recreate a default feature. That used to work by default in the past.

I’ve tried them and they kind of seem to work, untill you get on frame 1 and press arrow left and for some reason goes to frame 2. After this occurs you get stuck on first 2 or last 2 frames depending on which key you press. 

Can i add you to the file so you can experience this yourself?

Is frame 1 your starting point, ​@Lenin? I set up a simple page with four frames and interactions (leaving out one from just so I knew for sure it wasn’t simply going from one frame to the next). I didn’t see what you describe with frame one. However, pressing the right-arrow key on the final frame goes back to the second to last frame. I could add another interaction to go back to the beginning, though. Here’s a screenshot of what I set up to test with:

Hi ​@adamsmasher ,

Yes frame 1 is my starting point, this is the interaction that i get. Also this interaction occures when you do this from the beginning frame (frame 1) and press left, you will get stuck between frame 1 and frame 2. I’ve added a screen capture.

Adding a interaction to proceed to the beginning isn’t viable for every use case when making a prototype that contains a specific flow with a start and an ending.

While presenting you do not want to reset your prototype and walk through the whole flow again. You want to be able to simple press your arrow keys for the previous path the frames where walked through.

I can’t tell what keys you are pressing from your video, though that is unusual that it goes back to Frame 2 from Frame 4, and then after that I see it just going back and forth between the first two frames - not what I saw with my own test file. Could you share your file with support-share@figma.com with edit access (this won’t affect your billing)? I’m going to create a ticket for you with our Technical Quality team so they can investigate. Thanks!