Small interactions can make a webpage easier to use: opening a tip, changing a setting, or reusing an interface component.
What You Need to Know
New browser features move through stages of availability. Check actual support across your audience's browsers before relying on an attribute, even if documentation already describes it.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<button type="button" commandfor="help-dialog" command="show-modal">Open help</button>
<dialog id="help-dialog">
<h2>Help</h2>
<p>Declarative commands need browser support.</p>
<form method="dialog"><button>Close</button></form>
</dialog>Let’s Read the Code
- <button>: The button offers an action; its type or command determines what happens.
- <dialog>: Dialog provides a browser-managed dialog container; modal display may need showModal or a supported command.
- type: Type changes what sort of control or resource the browser uses.
- commandfor: Commandfor identifies the element a declarative command button should control.
What the example shows: Before using an emerging feature, check whether it is broadly supported, limited support, or experimental.
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
Compare the declarative command with a showModal() JavaScript fallback on an older browser.
Common Beginner Mistakes
- Assuming new HTML syntax works in every browser without testing.
- Do not assume that seeing an element in documentation means it is safe for every production audience.
Key Takeaways
- New browser features move through stages of availability.
- <button>: The button offers an action; its type or command determines what happens.
- Test the behavior you expect rather than trusting how the snippet looks in your editor.