Navigate to frame in Figma - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select a frame by its name in Figma plugin API.

Figma

const frame = figma.currentPage.[1](node => node.name === 'Frame 1');

Drag options to blanks, or click blank then click option'

AgetNode

BfindAll

CfindChild

DfindOne

Attempts:

3 left

💡 Hint

Common Mistakes

Using findAll returns an array, not a single frame.

Using getNode is not a valid method on currentPage.

The findOne method returns the first node matching the condition, which is used to find a frame by name.

2fill in blank

medium

Complete the code to navigate the viewport to the selected frame.

Figma

figma.viewport.[1](frame);

Drag options to blanks, or click blank then click option'

AscrollAndZoomIntoView

BzoomToNode

CfocusOnNode

DmoveToNode

Attempts:

3 left

💡 Hint

Common Mistakes

zoomToNode is not a valid Figma viewport method.

focusOnNode does not exist in Figma API.

The scrollAndZoomIntoView method moves the viewport to show the specified node.

3fill in blank

hard

Fix the error in the code to correctly find a frame named 'Dashboard'.

Figma

const dashboard = figma.currentPage.[1](node => node.name === 'Dashboard' && node.type === 'FRAME');

Drag options to blanks, or click blank then click option'

AfindAll

BgetNodeByName

CfindOne

Dfilter

Attempts:

3 left

💡 Hint

Common Mistakes

Using findAll returns an array, causing errors when assigning to a single variable.

getNodeByName is not a valid method.

findOne returns the first node matching the condition, which is correct here. findAll returns an array, and filter is not a method on currentPage.

4fill in blank

hard

Fill both blanks to select a frame named 'Settings' and navigate the viewport to it.

Figma

const settingsFrame = figma.currentPage.[1](node => node.name === 'Settings' && node.type === 'FRAME');
figma.viewport.[2](settingsFrame);

Drag options to blanks, or click blank then click option'

AfindOne

BscrollAndZoomIntoView

CfindAll

DzoomToNode

Attempts:

3 left

💡 Hint

Common Mistakes

Using findAll returns an array instead of a single frame.

Using zoomToNode is not a valid viewport method.

Use findOne to get the frame and scrollAndZoomIntoView to move the viewport.

5fill in blank

hard

Fill all three blanks to find a frame named 'Profile', check if it exists, and then navigate the viewport to it.

Figma

const profileFrame = figma.currentPage.[1](node => node.name === 'Profile' && node.type === 'FRAME');
if (profileFrame !== [2]) {
  figma.viewport.[3](profileFrame);
}

Drag options to blanks, or click blank then click option'

AfindOne

Bnull

CscrollAndZoomIntoView

Dundefined

Attempts:

3 left

💡 Hint

Common Mistakes

Checking against undefined instead of null may cause logic errors.

Using findAll returns an array, causing errors in the if condition.

Use findOne to find the frame, check against null to confirm it exists, then use scrollAndZoomIntoView to move the viewport.

Practice

1. What does the Navigate to frame action do in Figma prototypes?

easy

A. It jumps to a specific screen or frame in your prototype.

B. It changes the color of the selected frame.

C. It exports the current frame as an image.

D. It duplicates the selected frame.

Solution

1. Step 1: Understand the purpose of navigation in prototypes

   Navigation allows users to move between different screens or frames to simulate app behavior.

2. Step 2: Identify what Navigate to frame specifically does

   This action directs the prototype to jump to a chosen frame when triggered.

3. Final Answer:

   It jumps to a specific screen or frame in your prototype. -> Option A

4. Quick Check:

   Navigate to frame = jump to screen [OK]

Hint: Remember: Navigate means jump to a screen [OK]

Common Mistakes:

• Confusing navigation with styling changes
• Thinking it exports or duplicates frames
• Assuming it edits frame content

2. Which of the following is the correct way to set a Navigate to frame action in Figma?

easy

A. Select a frame and type its exact name in the action settings.

B. Select any frame and leave the name blank.

C. Use a random name for the frame in the action settings.

D. Select a frame and set the action to 'Export frame'.

Solution

1. Step 1: Check how Figma identifies frames for navigation

   Figma requires the exact frame name to correctly link navigation actions.

2. Step 2: Understand the importance of exact naming

   Using the exact frame name avoids errors and ensures the prototype jumps to the right screen.

3. Final Answer:

   Select a frame and type its exact name in the action settings. -> Option A

4. Quick Check:

   Exact frame name needed for navigation [OK]

Hint: Always use exact frame names for navigation [OK]

Common Mistakes:

• Leaving frame name blank causes navigation failure
• Using incorrect or random frame names
• Confusing navigation with export actions

3. Given a prototype with frames named Home, Profile, and Settings, what happens if you set a Navigate to frame action to Profile from the Home frame?

medium

A. The prototype jumps to the Settings frame.

B. The prototype shows an error and stops.

C. The prototype jumps to the Profile frame.

D. The prototype stays on the Home frame.

Solution

1. Step 1: Identify the target frame name in the navigation action

   The action is set to navigate to the Profile frame.

2. Step 2: Understand the effect of the navigation action

   When triggered, the prototype moves from Home to the Profile frame.

3. Final Answer:

   The prototype jumps to the Profile frame. -> Option C

4. Quick Check:

   Navigate to 'Profile' = jump to Profile frame [OK]

Hint: Navigation goes exactly to the named frame [OK]

Common Mistakes:

• Confusing target frame with other frames
• Assuming navigation fails without error
• Thinking it stays on the current frame

4. You set a Navigate to frame action to a frame named Dashboard, but when you test the prototype, it does not navigate and stays on the current frame. What is the most likely cause?

medium

A. The frame Dashboard is hidden in the layers panel.

B. The frame name Dashboard is misspelled in the action settings.

C. The prototype does not support navigation actions.

D. You forgot to select the trigger for the navigation.

Solution

1. Step 1: Check the frame name spelling in the navigation action

   Navigation requires the exact frame name; a misspelling causes failure.

2. Step 2: Consider other possible issues

   While triggers and visibility matter, the most common cause is a typo in the frame name.

3. Final Answer:

   The frame name Dashboard is misspelled in the action settings. -> Option B

4. Quick Check:

   Misspelled frame name blocks navigation [OK]

Hint: Check spelling of frame names first [OK]

Common Mistakes:

• Ignoring spelling errors
• Assuming prototype disables navigation
• Overlooking trigger setup

5. You want to create a prototype where clicking a button on the Login frame navigates to either Dashboard or Error frames based on user input. How can you set up navigation to handle this conditional flow in Figma?

hard

A. Figma does not support conditional navigation; you must export and code it externally.

B. Use a single Navigate to frame action and type both frame names separated by a comma.

C. Set the navigation action to Dashboard and rename the Error frame to Dashboard.

D. Create two buttons with separate Navigate to frame actions for Dashboard and Error frames, triggered by different user inputs.

Solution

1. Step 1: Understand Figma's navigation capabilities

   Figma supports navigation triggered by user actions but does not support conditional logic inside a single action.

2. Step 2: Implement conditional navigation using multiple buttons or triggers

   Create separate buttons or triggers for each navigation path, each with its own Navigate to frame action.

3. Final Answer:

   Create two buttons with separate Navigate to frame actions for Dashboard and Error frames, triggered by different user inputs. -> Option D

4. Quick Check:

   Use multiple triggers for conditional navigation [OK]

Hint: Use separate buttons for each navigation path [OK]

Common Mistakes:

• Trying to list multiple frames in one action
• Renaming frames incorrectly
• Assuming Figma supports complex conditions natively