Let’s take one interactive feature apart so the markup and behavior make sense separately.
What You Need to Know
Details has an open state that indicates whether its content is visible. Script can listen for toggle changes, but opening and closing the basic disclosure does not require script.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<details>
<summary>How long should I practice?</summary>
<p>Ten focused minutes a day is a good start.</p>
</details>Let’s Read the Code
- <details>: Details makes a section expandable without requiring a custom script.
- <summary>: Summary is the label people activate to expand or collapse details.
Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.
What Happens in the Browser?
When this example includes JavaScript, it supplies behavior that ordinary HTML does not automatically provide. Always think about a fallback.
Start with native behavior. Details, dialog, and popover each solve a different interface problem. Choose the simplest control that actually matches what a visitor wants to do, then test focus and dismissal as well as appearance.
Your Turn
Run this on a local development server if it loads modules or resources. Change the visible text or trigger and check what still works with scripts disabled.
Common Beginner Mistakes
- Assuming new HTML syntax works in every browser without testing.
- HTML supplies structure; JavaScript is necessary for the scripted behavior in this example. Check keyboard access and focus movement too.
Key Takeaways
- Details has an open state that indicates whether its content is visible.
- <details>: Details makes a section expandable without requiring a custom script.
- Test the behavior you expect rather than trusting how the snippet looks in your editor.