On this page
@addTagHelper *, Webority.Ui.RazorAlignment
Choose start for a destructive action on its own, or between to split a cancel and submit pair.
Start-aligned delete
Cancel and submit split
Common patterns
Three footers that cover most forms: one primary action, a cancel and confirm pair, and a destructive action beside cancel.
Single primary action
Cancel and confirm pair
Destructive action beside cancel
Every option
Every value of every prop, one cell each.
children
children: the app-button elements inside the footer (React: children)
align
align="end" (default): one action
align="start": destructive action alone
align="between": cancel and submit pair
sticky
sticky off (default): inline, no sticky class
sticky: top border and surface background, sticks to the viewport bottom
class
class: extra classes on the root element (React: className)
Guidance
What to do, and what to avoid.
Use it when
- A form has action buttons at the end (submit, save, cancel, etc.).
- A form is longer than one viewport and needs actions to stay visible (use sticky).
- You need consistent button alignment across all forms (trailing, leading, or space-between).
Reach for something else when
- Buttons are inside a modal or dialog → AppModal or AppConfirmDialog own the footer logic
- You need custom spacing or layout around buttons → Use a raw flex/grid container for full control
- Buttons are scattered throughout the form, not grouped at the end → Use AppButton directly where needed
Reference
Try every prop, read the full list, and check keyboard and screen reader behaviour.
3 props. The 2 most used come first.
Used on most screens 2 props
| Prop | Type | Default | Description |
|---|---|---|---|
| aligndefault end | end | start | between | end | Alignment of the children: end, start or between. |
| stickydefault false | bool | false | Sticks the actions to the bottom of the viewport with a border and background. |
Less common 1 props
| Prop | Type | Default | Description |
|---|---|---|---|
| (content)default - | - | - | Action buttons (app-button, action-icon, etc.). |
Screen reader
3 notes- Renders a plain div with the form-actions class. It adds no role or label, so each button keeps its own accessible name.
- The tab order follows the order of the children; align changes only where they sit, not their order.
- Extra attributes such as aria-label pass through to the div.