Skip to main content
Question

Prototype mode skips connected frames when using arrow keys

  • May 6, 2026
  • 3 replies
  • 24 views

Anna_Paramonova

Hi everyone,

I’m having an issue with Figma Prototype mode.

Previously, all frames connected within one flow were shown when navigating through the prototype with the arrow keys. Now, some connected frames are skipped and don’t appear in Prototype mode, even though they are connected in the flow.

I also tested this in another file with another design, but the same issue still happens.

I don’t understand what changed or how to fix it. Is this expected behavior, a known bug, or is there any workaround?

Thanks!

3 replies

Jaycee Lewis
Figmate

Hi,, ​@Anna_Paramonova 👋 Welcome to our community! Prototype flows acting up across multiple files usually points to something repeatable — which is good, means we can probably pin it down.

Could you grab a screen recording? Screenshots work too. Expanding the Prototype tab in the right sidebar before you trigger the issue is helpful for “seeing” what’s happening.

If it's already cleared up, no need — just let me know. Talk soon! — Jaycee


Anna_Paramonova

Hi ​@Jaycee Lewis,

Thanks for your reply. I’ve attached a screen recording here.

In the example, there are five frames connected within one flow. One of them is connected as an overlay, and the others use “Navigate to” interactions.

The clickable prototype itself works: when I use the connected buttons/areas, I can access all frames. The issue happens only when I navigate through the flow in Prototype View using the arrow keys — then only some frames are shown, while others are skipped.

As far as I remember, it used to be possible to go through all frames connected within one flow using the arrow keys in Prototype View, so I’m not sure why this is happening now.

Thanks!


adamsmasher
Figmate

Hi ​@Anna_Paramonova! Stepping in for ​@Jaycee Lewis.

 

Thanks for the video - it’s super helpful to see what you are describing with your actual file and I can see why it’s a bit confusing. I did some digging on our end and found that we fixed a bug that I think has caused the change in behavior for you, along with a solution you can try. The bug would cause using the next/prev navigation to sometimes behave like a slideshow (what you were expecting), and sometimes follow interaction flow (which is what was intended). With that bug fixed, navigating with the arrow keys will follow interaction flows in specific, which I think is why in your video when you use the next key on the navigation frame it follows the interaction to the karte frame.

 

For a solution, you’ll want to add the following interactions to each frame:

  1. On KeyPress (Left Arrow) -> Navigate To (destination is the frame to the left)
  2. On KeyPress (Right Arrow) -> Navigate To (destination is the frame to the right)

While this requires adding additional interactions, it can also give you extra control over what order these are in; this can be helpful on more complex prototyping where you may want to organize them in different ways on the canvas.

 

Let me know if I’ve misunderstood what you are seeing, or if you see something else unexpected after adding those additional interactions. Cheers!