Button

Take inputButton

Button is part of the Basic Catalog in Google's A2UI v1.0 protocol. This page shows how it behaves so you can build with it. Unofficial, and not affiliated with Google.

Live preview

What you try is exactly what we tested
variant (allowed values only)
Recorded snapshot · React 0.15.0 with web_core 0.15.0 · 2026-11-14Live · rendered in your browser by @a2ui/react 0.15.0
Recorded render of Button (minimal)

What it is

A clickable button that dispatches an action. Supports 'primary' and 'borderless' variants.

In the trip planner

The trip planner, a worked example built only from Basic Catalog parts, uses 2 Button parts: Save plan and Change dates; pressing one sends an action to the agent. See it running, with every part numbered.

Counted from one real request (Oslo, 3 days (Basic components only, text version), 32 parts, 2026-11-14).

Properties

Schema properties for Button
PropertyTypeRequiredAllowed valuesNew in 1.0
childChildyes–
variantstringnodefault, primary, borderless
actionActionyes–

Evidence

PASS React 0.15.0 with web_core 0.15.0, v1.0 module · headless Chromium, Linux · 2026-11-14 · 1 run

What is not claimed

  • Other renderers (Lit, Angular, community) were not rerun; the 8 November 2026 matrix stands.
  • Gemini Enterprise was not tested in this run (14 November 2026).
  • Remote media was not loaded, so media records element creation and attributes, not playback.
  • Layout and visual quality are not judged.

Media and links in the examples use example.invalid placeholders. Navigation is intercepted and media is not played.

Findings

No findings recorded for this component.

Recorded cases

Recorded cases for Button
CaseExpectedObservedVerdict
click -> action name + literal contextone action go with the literal contextPASS
context value bound to data pathcontext values read from the data modelPASS
context resolved at click time (model updated between clicks)context resolved at click timePASS
context value = formatString callformatString result in the contextPASS
two clicks -> two callbackstwo clicks, two actionsPASS
no context keyaction with an empty contextPASS
button inside List template, relative context path; click 2ndrelative path resolves per itemPASS
checks required(/name): disabled -> fill model -> enabled -> clickdisabled while invalid, enabled once valid, then firesPASS
and/or/not check composition -> disabled flagsand, or, not as check conditions drive the disabled state (covered value by value in the function cases below)observed {"dis": ["AND:true", "OR:false", "NOT:true"], "dis2": ["AND:false", "OR:false", "NOT:true"]}OBSERVED