client:visible for viewport-based loading in Astro - Step-by-Step Execution

Concept Flow - client:visible for viewport-based loading

Page loads

↓

Component marked client:visible

↓

Browser checks if component is in viewport

↓

Component renders and runs client code

This flow shows how Astro waits to load and run a component's client code only when it becomes visible in the browser viewport.

Execution Sample

Astro

<div>My Widget</div>

<script>
  console.log('Widget loaded')
</script>

This Astro component logs 'Widget loaded' only when it scrolls into view.

Execution Table

Step	Event	Viewport Check	Action	Output
1	Page loads	Component not visible	Do not load client code	No console log
2	User scrolls	Component enters viewport	Load and hydrate component	Console logs 'Widget loaded'
3	User scrolls away	Component exits viewport	Component remains loaded	No new logs
4	User scrolls back	Component re-enters viewport	No reload needed	No new logs

💡 Component client code loads only once when it first becomes visible in viewport.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
componentVisible	false	false	true	false	true
clientCodeLoaded	false	false	true	true	true

Key Moments - 2 Insights

Why doesn't the client code run immediately on page load?

Because the component is marked with client:visible, Astro waits until the component enters the viewport before loading and running its client code, as shown in execution_table step 1.

What happens if the user scrolls past the component and then back again?

The client code loads only once when the component first becomes visible. Scrolling away and back does not reload it, as shown in execution_table steps 3 and 4.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the client code load?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Action' column where it says 'Load and hydrate component'.

According to variable_tracker, what is the value of clientCodeLoaded after step 1?

A false

B true

C undefined

D null

💡 Hint

Look at the 'clientCodeLoaded' row under 'After Step 1' column.

If the component was visible on page load, how would the execution table change?

A Client code never loads

B Client code loads at step 3

C Client code loads at step 1

D Client code loads at step 4

💡 Hint

If visible immediately, loading happens right away, not waiting for scroll.

Concept Snapshot

Astro's client:visible loads client code only when component enters viewport.
Page loads without running client code if component is offscreen.
When user scrolls component into view, Astro hydrates it.
Client code runs once, no reload on scrolling away and back.
Great for performance by delaying work until needed.

Full Transcript

The client:visible directive in Astro delays loading and running client-side code for a component until it becomes visible in the browser viewport. When the page first loads, if the component is offscreen, Astro does not load its client code. Once the user scrolls and the component enters the viewport, Astro loads and hydrates the component, running its client code. This happens only once; scrolling away and back does not reload the code. This approach improves performance by loading code only when needed.

Practice

1. What does the client:visible directive do in Astro?

easy

A. It loads a component only when it appears in the user's viewport.

B. It loads a component immediately when the page loads.

C. It prevents a component from ever loading.

D. It loads a component only on server side.

Solution

1. Step 1: Understand the purpose of client:visible

   This directive delays loading until the component is visible on screen, saving resources.

2. Step 2: Compare options with this behavior

   Only It loads a component only when it appears in the user's viewport. matches this behavior; others describe immediate or no loading.

3. Final Answer:

   It loads a component only when it appears in the user's viewport. -> Option A

4. Quick Check:

   client:visible = loads on viewport [OK]

Hint: Remember: client:visible means load when visible on screen [OK]

Common Mistakes:

• Thinking it loads immediately on page load
• Confusing with server-side loading
• Assuming it never loads the component

2. Which of the following is the correct syntax to load a component only when visible using Astro?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall Astro client directives

   Astro uses client:visible to load components on visibility.

2. Step 2: Match syntax with directive

   Only uses client:visible correctly in JSX-like syntax.

3. Final Answer:

   <Component client:visible /> -> Option B

4. Quick Check:

   Correct directive syntax = [OK]

Hint: Use client:visible exactly as attribute on component [OK]

Common Mistakes:

• Using client:load instead of client:visible
• Confusing with client:idle or client:only
• Missing the colon in client:visible

3. Given this Astro code snippet, what will happen when the page loads?

<Image src="photo.jpg" alt="Photo" client:visible />

medium

A. The image never loads.

B. The image loads immediately when the page loads.

C. The image loads only when it scrolls into the viewport.

D. The image loads only after a user clicks it.

Solution

1. Step 1: Understand client:visible effect on image

   The image will not load immediately but waits until visible on screen.

2. Step 2: Analyze options for loading behavior

   The image loads only when it scrolls into the viewport. correctly states loading on scroll into viewport; others are incorrect.

3. Final Answer:

   The image loads only when it scrolls into the viewport. -> Option C

4. Quick Check:

   client:visible delays load until visible [OK]

Hint: client:visible delays loading until visible on screen [OK]

Common Mistakes:

• Assuming image loads immediately
• Thinking it loads on click
• Believing it never loads

4. Identify the error in this Astro component usage:

<Video src="movie.mp4" client-visible />

medium

A. The src attribute is missing.

B. The directive client-visible is correct syntax.

C. The component tag should be self-closing with a slash at the end.

D. The directive should be client:visible with a colon, not a dash.

Solution

1. Step 1: Check directive syntax

   Astro directives use colon, so client:visible is correct, not client-visible.

2. Step 2: Verify other attributes and syntax

   The src attribute is present, and self-closing slash is optional in JSX-like syntax.

3. Final Answer:

   The directive should be client:visible with a colon, not a dash. -> Option D

4. Quick Check:

   Directive syntax requires colon, not dash [OK]

Hint: Use colon in client:visible, not dash [OK]

Common Mistakes:

• Using dash instead of colon in directive
• Thinking self-closing slash is mandatory
• Missing src attribute (which is present here)

5. You want to optimize a page with many interactive widgets using client:visible. Which approach best improves performance without hurting user experience?

hard

A. Apply client:visible only to widgets below the fold, load above-the-fold normally.

B. Apply client:visible to all widgets, including those visible on initial load.

C. Avoid using client:visible and load all widgets immediately.

D. Use client:visible only on images, not interactive widgets.

Solution

1. Step 1: Consider user experience for above-the-fold content

   Widgets visible immediately should load right away for smooth interaction.

2. Step 2: Use client:visible for below-the-fold widgets

   Delaying load for widgets off-screen saves data and speeds initial load.

3. Step 3: Evaluate options

   Apply client:visible only to widgets below the fold, load above-the-fold normally. balances performance and experience; others either delay too much or avoid optimization.

4. Final Answer:

   Apply client:visible only to widgets below the fold, load above-the-fold normally. -> Option A

5. Quick Check:

   Optimize below fold with client:visible, load above fold immediately [OK]

Hint: Use client:visible only for off-screen widgets to keep UX smooth [OK]

Common Mistakes:

• Applying client:visible to all widgets including visible ones
• Not using client:visible at all
• Limiting client:visible only to images