Skip to content
Razor catalogue

On this page

@addTagHelper *, Webority.Ui.Razor

Alignment

Choose start for a destructive action on its own, or between to split a cancel and submit pair.

Start-aligned delete
Show code
<app-form-actions align="Start">
    <app-button tone="Danger" variant="Outline">Delete</app-button>
</app-form-actions>
Cancel and submit split
Show code
<app-form-actions align="Between">
    <app-button variant="Outline">Cancel</app-button>
    <app-button>Submit</app-button>
</app-form-actions>

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
Show code
<app-form-actions>
    <app-button>Save</app-button>
</app-form-actions>
Cancel and confirm pair
Show code
<app-form-actions align="Between">
    <app-button variant="Outline">Cancel</app-button>
    <app-button>Confirm</app-button>
</app-form-actions>
Destructive action beside cancel
Show code
<app-form-actions align="Between">
    <app-button tone="Danger" variant="Outline">Delete Account</app-button>
    <app-button variant="Outline">Cancel</app-button>
</app-form-actions>

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.

end start between
React, generated from the controls
<AppFormActions>
  <AppButton variant="outline">Cancel</AppButton>
  <AppButton>Save changes</AppButton>
</AppFormActions>
Razor, the same props
<app-form-actions>
    <app-button variant="Outline">Cancel</app-button>
    <app-button>Save changes</app-button>
</app-form-actions>

3 props. The 2 most used come first.

Used on most screens 2 props

PropTypeDefaultDescription
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

PropTypeDefaultDescription
(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.