Modal pattern with intercepting routes in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the modal pattern with intercepting routes in Next.js?

It is a way to show a modal dialog by intercepting navigation routes, so the modal appears over the current page without a full page reload.

intermediate

How does Next.js detect when to show a modal using intercepting routes?

Next.js compares the current route with the previous route and shows the modal if the new route is a child or overlay route, keeping the background page visible.

intermediate

Why use intercepting routes for modals instead of traditional modal state?

Interception keeps the URL in sync with the UI, allows browser navigation (back/forward), and supports deep linking directly to modal content.

beginner

What React hook is commonly used to track route changes for modal interception in Next.js?

The usePathname hook from 'next/navigation' is used to detect route changes and decide when to show or hide the modal.

advanced

What accessibility considerations should you keep in mind when implementing modals with intercepting routes?

Ensure focus is trapped inside the modal, provide ARIA labels, allow keyboard navigation, and restore focus to the background page when modal closes.

What does the modal pattern with intercepting routes primarily help with in Next.js?

A Showing modals without full page reloads

B Improving server-side rendering speed

C Automatically generating routes

D Styling modals with CSS

The pattern allows modals to appear over the current page by intercepting route changes, avoiding full page reloads.

Which Next.js hook helps detect route changes for modal interception?

A usePathname

B useState

C useEffect

D useContext

usePathname provides access to the current pathname needed to detect navigation changes.

What is a key benefit of using intercepting routes for modals?

A Disables page scrolling permanently

B Automatically styles modals

C Prevents modals from closing

D Supports browser back and forward buttons

Intercepting routes keep URL in sync, so browser navigation works naturally with modals.

When a modal is open via intercepting routes, what remains visible?

A Only the modal content

B The background page behind the modal

C A blank white screen

D The browser console

The background page stays visible behind the modal to maintain context.

Which accessibility feature is important for modals with intercepting routes?

A Disabling keyboard navigation

B Removing ARIA labels

C Focus trapping inside the modal

D Hiding modal from screen readers

Focus trapping ensures keyboard users stay inside the modal until it closes.

Explain how the modal pattern with intercepting routes works in Next.js and why it improves user experience.

Think about how the URL and page content stay in sync when opening a modal.

Describe key accessibility practices to follow when implementing modals with intercepting routes in Next.js.

Consider how users with keyboards or screen readers interact with modals.

Practice

1. What is the main benefit of using the modal pattern with intercepting routes in Next.js?

easy

A. It automatically reloads the entire page when opening a modal.

B. It allows showing a popup without leaving the current page.

C. It disables keyboard navigation while the modal is open.

D. It prevents any URL changes when interacting with the modal.

Solution

1. Step 1: Understand modal with intercepting routes

   This pattern lets you open a modal that overlays the current page content without navigating away.

2. Step 2: Identify the benefit

   Because the modal is shown on top, the user stays on the same page, improving user experience.

3. Final Answer:

   It allows showing a popup without leaving the current page. -> Option B

4. Quick Check:

   Modal pattern = popup without page change [OK]

Hint: Modals with intercepting routes keep you on the same page [OK]

Common Mistakes:

• Thinking the page reloads when modal opens
• Assuming URL never changes
• Believing keyboard navigation is disabled

2. Which Next.js feature is commonly used to control modal visibility with intercepting routes?

easy

A. Using URL query parameters to toggle modal state

B. Using React class components with state

C. Using server-side rendering to open modals

D. Using CSS hover effects to show modals

Solution

1. Step 1: Identify modal control method

   Next.js modals with intercepting routes often use URL query parameters to track if modal is open or closed.

2. Step 2: Eliminate incorrect options

   React class components are outdated; server-side rendering doesn't control modal visibility dynamically; CSS hover is unrelated to routing.

3. Final Answer:

   Using URL query parameters to toggle modal state -> Option A

4. Quick Check:

   Modal visibility = URL query param [OK]

Hint: Modal open state is often in URL query parameters [OK]

Common Mistakes:

• Confusing client state with URL state
• Using class components instead of hooks
• Relying on CSS hover for modal control

3. Given this Next.js snippet controlling a modal with query param ?modal=open:

const router = useRouter();
const isModalOpen = router.query.modal === 'open';

return (
  <>
    {isModalOpen && <ModalComponent />}
    <MainPageContent />
  </>
);

What happens when the URL changes from /page to /page?modal=open?

medium

A. The page reloads and shows a blank screen.

B. The main page content is replaced by the modal component.

C. Nothing changes because query parameters don't affect rendering.

D. The modal component appears over the main page content.

Solution

1. Step 1: Understand the code logic

   The code checks if the query parameter 'modal' equals 'open'. If yes, it renders the modal component alongside the main content.

2. Step 2: Analyze URL change effect

   Changing URL to include '?modal=open' sets isModalOpen true, so modal appears over the main page without replacing it.

3. Final Answer:

   The modal component appears over the main page content. -> Option D

4. Quick Check:

   Query param 'modal=open' = modal visible [OK]

Hint: Query param 'modal=open' triggers modal display [OK]

Common Mistakes:

• Thinking modal replaces main content
• Ignoring query parameters in rendering
• Assuming page reloads on query change

4. Consider this Next.js modal code snippet:

const router = useRouter();
const isModalOpen = router.query.modal === 'open';

function closeModal() {
  router.push('/page');
}

return (
  <>
    {isModalOpen && <Modal onClose={closeModal} />}
    <PageContent />
  </>
);

What is a likely bug in this code regarding accessibility?

medium

A. The URL does not update when the modal opens.

B. The modal never closes because router.push is incorrect.

C. Keyboard focus is not moved to the modal when it opens.

D. The modal content is rendered outside the React tree.

Solution

1. Step 1: Review modal accessibility needs

   When a modal opens, keyboard focus should move inside it for screen reader and keyboard users.

2. Step 2: Check code for focus management

   The code changes URL and renders modal but does not handle moving keyboard focus to modal.

3. Final Answer:

   Keyboard focus is not moved to the modal when it opens. -> Option C

4. Quick Check:

   Modal accessibility = move keyboard focus [OK]

Hint: Always move keyboard focus into modal on open [OK]

Common Mistakes:

• Ignoring keyboard focus management
• Assuming URL push closes modal automatically
• Confusing rendering with accessibility

5. You want to implement a modal in Next.js that opens on /gallery?modal=photo123 and closes by removing the query param, without losing the gallery scroll position. Which approach best achieves this?

hard

A. Use router.push with shallow: true to update URL without full reload and keep scroll.

B. Use router.replace without shallow to reload page and reset scroll.

C. Use window.location.href to change URL and force reload.

D. Use CSS to hide modal and ignore URL changes.

Solution

1. Step 1: Understand shallow routing in Next.js

   Shallow routing updates the URL without running data fetching methods or reloading the page, preserving scroll and state.

2. Step 2: Apply shallow routing to modal open/close

   Using router.push with shallow: true changes query params to open/close modal without losing scroll position.

3. Final Answer:

   Use router.push with shallow: true to update URL without full reload and keep scroll. -> Option A

4. Quick Check:

   Shallow routing = URL change without reload [OK]

Hint: Use shallow routing to keep scroll when changing URL [OK]

Common Mistakes:

• Using router.replace without shallow reloads page
• Using window.location.href causes full reload
• Ignoring URL for modal state control