Feedback
Alert
Severity semantics, inline layout, optional actions, and explicit dismissal — never a toast.Anatomy
The public structure is divided into four responsibilities.
- 1
Surface root
Carries the container role, shape, and the status or alert semantics.
- 2
Leading icon
An optional decorative glyph supplied explicitly through icon or replaced with the polymorphic icon slot.
- 3
Content
Title and body wire the accessible name and description; empty wrappers never render.
- 4
Actions and close
Consumer buttons in the actions slot, plus the optional dismiss control.
Interactive configuration
Adjust severity, variant, and dismissal, then choose a coherent content preset.
Severity owns color
There is no free-form color prop that could contradict the announced severity.
Not a snackbar
Transient confirmation of a completed action belongs to MSnackbar, not to an inline alert.
States
States preserve accessibility and expected feedback.
Polite status
The message is announced politely without interrupting the current task.
Assertive alert
Error maps to role=alert and interrupts, because the user is blocked.
Explicit dismissal
The close control emits close and hides the alert; Escape never dismisses it.
Rendered with the page
Alerts already present in SSR HTML render as a named group without announcements.
A failed table request
The alert stays next to the affected dataset and offers recovery without replacing the table shell.
Service | Status | Updated |
|---|
Conditional template state
A template branch introduces persistent feedback only while an unpublished draft exists.
Release notes template
Customer-facing summary
The template is shared by every production release.